NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Wireless devices connected to same AP can't see each other
I have and MR60 and two MS60. If two wireless devices are connected to the network via the MR60 they can not see each other / connect to each other / access each other. However both devices can be s...
Ok, the only thing coming into my mind is disabling the Loop Prevention on the GS908E. The point is these consumer Mesh systems don't come with STP (RSTP, MTP) support, and implement custom tricks to stop loops when having the wireless backhaul (always active, even on a poor connection) and a wired backhaul plugged.
We have some more active members with a lot more practical insight on the Nighthawk Mesh system - I'm more an SMB and business network person. I hope we can get in some Netgear engineers - nothing obvious causing some connections shutdown (this is what happens on your MR60 and the MS60 WiFi each). DarrenM please.
Well I decided to do some additional testing today. I shut down all the MS60 and disconnected the MR60 from the switch. And still all devices wirelesses connected o it had issues. So clearly an issue with the MR60 and how it is routing things.
I spent time going through settings, and found the culprit (though I think it is a different culprit than last time as I don't recall ever messing with it).
under Advance->Security->Access Control "Turn on Access Control" was checked, rule was set to "allow all new devices to connect" all devices listed (wired and wireless) were set to allowed.
So nothing obvious that it would be the culprit, but I went I'm testing things...
So I unchecked it and thus disabled Access Control and now all devices connected wirelessly to to MR60 can see see each other.
Please allow one clarification: What happens on the LAN within the one and only IP subnet, regardless if the switches are connected, or just the wireless backhaul is active it's all L2 switching - or bridging between the wireless stations and the router/satellite radio. The only routing is on the MR60 where it does the many2one NAT for the LAN IP addresses and devices, along with the port forwarding.
Are all your MR60 and MS60 operating on the current firmware version 1.1.7.134 (dated from the 2nd January 2023 - so a looong time without mandatory updates)?
Either there is something really broken (hard to imagine because of Netgear is selling these kits in masses) - a good starting point would be a factory reset on the MR60 and all MS60 - or I have to find some MK6x system in the free market an buy me a new toy and test bed for the community on Christmas.
Yes, all of them are on that firmware
As I stated, I found the problem it's the "Access control" it was turned on, and for whatever reason when it is on it blocks communication between wireless devices who are both connected to the MR60 but not with wired devices or any wireless devices connected to an MS60. Though nowhere does it seem to indicate that this would behave in such a way. I'm guessing the default state is it for it to be off, so most do not encounter this issue. And with the way the settings it had it wasn't restricting any devices from connecting, so no need to be on, so turning it off causes no issue and fixed the issue I was having 🙂 while I could try and figure more out about it, and am curious why that setting caused this behavior, for now I am done with it until it starts messing up again...
One other possibility is that for MK systems and Orbi MESH systems, they don't seem to like IGMP or Green Ethernet protocols that are seen on some Managed switches. Some have been able to disable these and has resolved some ethernet connected satellite issues seen with manages switches. Otherwise, it's recommended to use non managed switches between the MR and MS if the MS are ethernet connected. I've had my 60 series connected before and haven't seen any issues in between them. NG GS-105/108v4 and GS308v3 series switches work for Nighthawk mesh systems
