NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MR60/MS60: cannot ping wired devices from wifi network
With the MR60 + 2*MS60 configured as a router, my wired devices (e.g. a Synology NAS) could not be seen from my wifi devices (e.g. a Macbook Air), and vice-versa, but wifi devices could see one anoth...
OK, thanks -- I have just posted it to the "ideas" forum. But to be frank, this is more of a bug report than an idea. If you own a wired printer or a wired NAS and you connect it to your home network, you certainly want to be able to reach it from your home wifi devices.
Hi,
Believe this bug is the same reason why I am having issue with my WiFi in combination with Google home.
My MR60 is wired connected with my ms60 via a switch. Problem is devices connected with the ms60 can't communicate with devices connected to my MR60.
Believe this bug is the same reason why I am having issue with my WiFi in combination with Google home.
My MR60 is wired connected with my ms60 via a switch. Problem is devices connected with the ms60 can't communicate with devices connected to my MR60.
I am pretty sure that this is a bug, but in spite of my having followed the moderator's advice and posted the issue to the suggestions area (which is ironic for a bug report), there has been no response and no firmware update. On the other hand, my workaround of using the netgear router in tandem with my old router (reported above in this thread) is still working very well for me. I do like the netgear system's mesh networking for covering the entire house. I just wish that this bug could be addressed so that I could eventually retire my old router.
We resolved this last week, thanks to Jason in L2 support. I posted a longer message in another thread. Issue was synology NAS firewall had rules set to allow 192.168.0.* whereas new MR60 router switched over to 192.168.1.*, so even though NAS was getting 192.168.1.* LAN address via DHCP from MR60, its firewall was rejecting local pings. As far as I can tell, it was "user error" on my part.