NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cannot ping the device in same network (MR60)
Switched to this device 3 days ago and having a hardtime managing my network since then. Worst customer-care support ever even with premium support Spend Three hours on calls all-together today wit...
It's been two months now since Netgear gave me the beta firmware to use (V1.0.6.103_21.03.03_homepod) and there is still no fix for this issue in the offical stable firmware.
I'd be fine with continuing to use this beta firmware but the actual throuthput performance is terrible. Transferring data across the network is excrutiatingly slow. I'm not able to stream plex video to my TV from another computer on the network. What is strange is that access to the internet seems to be uneffected and is full speed.
I'm not sure if the performance issue is a side effect of whatever workaround/fix they implemented to get wifi devices to be able to reliably communicate or if this beta firmware has some kind of special kernel-level debugging enabled (which usually degrades performance). Either way I just can't handle this. I need this fixed or I need to switch to another model and brand of hardware. This system is broken.
Another unforunate thing is that I have this same mesh system installed in two locations (I bought it for my in-laws) and I have exactly the same issues with both systems. It's ridiculous that this gear is still for sale. Netgear needs to fix this.
When I call Netgear they want to charge me because I'm outside of my 90-day purchase window. Screw them.
Here are links to the beta firmware "V1.0.6.103_21.03.03_homepod" (hosted on Netgear's Salesforce instance)
This firmware resolves the issue where some devices could not reach each other on my local network. Now my kids can play their games together and I'm able to use my Apple Homepod devices. The downside is that LAN (but not WAN/internet) throughput seems to be reduced.
MR60-V1.0.6.103_21.03.03_homepod.chk
MS60-V1.0.6.103_21.03.03_homepod.chk
I've had pretty good luck with this firmware but your results may vary. Good luck.
Thanks for supplying that. I will have to test it out and see how it does for my environment. Nice to know they are at least aware and working on a fix - just wish they'd get it into the next full release quickly.
TBH, I have no idea how long those links will stay up. If they go down then I'll replace with links to my personal google drive.
I just want some transparency about the issue. The official firmware is legitimately broken.
While it did fix the problem, you were right in that it is slowed down on the local LAN.
I thought that would be acceptable in my environment but almost immediately I realized how much that actually does affect what we do at home. I have a Plex server and it was nearly impossible to locally stream anything to any TV in the house from my server due to the latency in the beta firmware. Oddly enough this was not something I had a problem with before the beta as most of the issues we had were related to file share access and of course inability to print to a printer from one laptop but not others which was the most annoying.
So, I went back to the latest firmware. For now, my only solution is to unplug the satellite and accept that not every system in the house will get as strong a signal.
I think you're right about them potentially having debug logging turned on in this beta firmware. Otherwise it was nice just to see a fix but I will have to hope they just get the fix into the next release.
Interesting why these didn't get posted to NGs download site:
I don't know why they didn't release these. Definitely don't install these if you don't trust them. I linked them from Netgear's Salesforce account to try to show that they came from Netgear.
Have the same problem , devices cannot ping any other device thats connected to sattelite , it can only ping if its connected to the main router . I think its some sort of inbuild firewall within the sattelite thats blocking certain traffic ( ICMP , Chromecast etc.) .
I can see all the device thats in same sattelite in the arp table , all devices are in same subnet(so no routing involved) , so most likely some Layer2 / mac filtering type of situation .
