× NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
× Introducing the new Orbi 770 Series Mesh System. To learn more click here.
Nighthawk Mesh WiFi

Welcome to the Nighthawk Mesh Community


Advanced Whole Home WiFi Click to Buy Nighthawk Mesh WiFi 6
Reply

MR60/MS60: cannot ping wired devices from wifi network

imjustabill
Guide

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 another.

 

Solution/workaround: I put my old TP-Link router back in place as a router, with wifi disabled, and then configured my MR60 as an access point.  Now my wired and wifi devices can all see one another.  I am back in business accessing my NAS from my Mac notebooks.  Unfortunately my upload speed in the workaround state is slower than with the MR60 in router mode, but at least my home network is now in a working state.  My wired devices (NAS + printer + voip telephone box) are attached to the MR60 ethernet port via a Netgear switch.  My old TP-link router now has just one ethernet cable to FIOS internet and one ethernet cable to the MR60 WAN port.

 

I would love to have some sort of firmware update that would allow traffic to/from the wired ports on the MR60/MS60 to be bridged/switched onto the wifi network, so that my wifii devices could talk with my wired NAS when the MR60 is in router mode.  Then I could finally discard my old TP-link router, which is slowing down my uploads, and whose security is probably less up-to-date than the new MR60's security.

 

Many thanks to Louie from customer support ticket # 43957276 who spent a lot of time trying several possible ideas to help me out via chat yesterday.  While we were not able to resolve the issue with the MR60 in router mode, I do appreciate the support.  I hope we can find out from the firmware experts whether this is a feature or a bug.

Message 1 of 6
Christian_R
NETGEAR Employee Retired

Re: MR60/MS60: cannot ping wired devices from wifi network

Hello imjustabill, 

 

Thank you for your interest in this feature. We recommend posting your suggestion on our Idea Exchange board. Our Product Managers review the board for great ideas to be implemented in future releases. Link is https://community.netgear.com/t5/Idea-Exchange-For-Home/idb-p/idea-exchange-for-home

 

Regards,

Christian 

Message 2 of 6
imjustabill
Guide

Re: MR60/MS60: cannot ping wired devices from wifi network

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.

 

Message 3 of 6
Desheba
Aspirant

Re: MR60/MS60: cannot ping wired devices from wifi network

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.
Message 4 of 6
imjustabill
Guide

Re: MR60/MS60: cannot ping wired devices from wifi network

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.

 

Message 5 of 6
imjustabill
Guide

Re: MR60/MS60: cannot ping wired devices from wifi network

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.

 

Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 2490 views
  • 0 kudos
  • 3 in conversation
Announcements

Orbi 770 Series