NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Nighthawk mesh MR60 - devices that require 2.4 GHz connection
Please be patient and descriptive in your replies, I pick things up pretty quickly but am far from a network engineer. I upgraded my entire network when the pandemic lockdown started due to my en...
Thank you so much worked for me...I turned off my 2 satellites and went into my garage. I connected all my smart outlets in there.
retromad wrote:My results with the nighthawk MR60 system is that devices on the same sid occassionally could not "see" each other unless they were also on the same frequency (e.g. 2.4 or 5).
Unanswered if this applies to the 2.4 or 5 GHz radio on the same device .... or if you try to state this applies "system wide" to router and all satellites. That would be very unlikely, because of the network frames travel all together over the wireless backhaul.
This might be a bug or unexpected limitation on the MR60/MS60 - all radio bands configured to the same SSID connect to the very same L2 network, the same broadcast domain.
Some of the devices were on 2.4 and some were on 5. I agree, there should be no difference at layer 2, however, the google minis in particular, seemed to not like being spread across both bands and would routinely drop off or not be visible/pingable. They would also inexplicably be reachable via the guest network during this time. This tells me there is something wonky (or a bug) with the way the mr60 is bonding or routing traffic across the bands on the same sid. If I can reach(ping) a device from the guest sid but not from its own sid that's a problem. It shouldn't be like it is, but it do...
This issue could also be partially due to having too many devices on the MR60 as I did have about 25 all connected in a mixed 2.4/5 sid. Maybe when these units are in heavy use or taxed they exhibit behaviors that have not been fully explored or documented by netgear?
Either way, upgrading to the orbi fixed all issues that I had.
For those still struggling to get 2.4 on your mr60 mesh. Just unplug all your satilites and cover your router in foil. Then go as far away as you can and check which band your on (should be 2.4). Using my house as an example, I had to go down a floor and to the opposite side of my house.
This issue could also be partially due to having too many devices on the MR60 as I did have about 25 all connected in a mixed 2.4/5 sid. Maybe when these units are in heavy use or taxed they exhibit behaviors that have not been fully explored or documented by netgear?
Either way, upgrading to the orbi fixed all issues that I had.
For those still struggling to get 2.4 on your mr60 mesh. Just unplug all your satilites and cover your router in foil. Then go as far away as you can and check which band your on (should be 2.4). Using my house as an example, I had to go down a floor and to the opposite side of my house.
Question: you say go as far away as you can, then check which band you're on. . .
How do you check which band you're on? I've seen no indicator on my phone that tells me if it's connected to 2.4 or 5. Thanks.
- On Android you long press the wifi button on the top pulldown menu then press the connected network (your sid). The network band is listed on the second item labled frequency. It will say either 2.4ghz or 5ghz.
It doesn't. It really doesn't. But thanks.
retromad wrote:
On Android you long press the wifi button on the top pulldown menu then press the connected network (your sid). The network band is listed on the second item labled frequency. It will say either 2.4ghz or 5ghz.
did the foil thing and it work ... sigh
I see Guest SSID always connecting to 2.4ghz, I am able to connect to my IOTs those need 2.4ghz connection type.
