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.
Agreed that the applications/connecting devices should not be dumb, however, If netgear is not going to let us have seperate sids, what would be nice is if they allowed us to choose what devices get what frequencies (filter via mac address). I have a house full of google home devices that cannot seem to understand that devices on a 2.4 network are on the same network as the 5 devices (I know google dumb). I would like to be able to just specifiy all Ghome devices as 2.4. I have them setup with reserved IP, how hard would it be to add a network frequency to this setting?
Aside from all this, we should be able to setup sids with frequencies, it is really dumb on netgears part that we cannot as the hardware in these units can do it. I should be able to setup a 2.4 and 5 ghz sid without putting foil on my router... :)
Any luck on your end resolving this problem?
I've had Amazon Echos go in and out of working or working oddly, I've had smart switches and plugs stop working, I had a devil of a time getting the garage door connected, and all around this 2.4Ghz/5.0Ghz issue. And then to face hostility when looking for answers, because the devices and apps are the problem? I'm with you, how hard could it be to just allow a setting for the "dumb" smart devices, so that everything plays nice?
So this issue and a host of google smart device issues has led me to believe that there is a deeper issue with how the nighthawk mesh devices bond the 2.4 and 5ghz channels. Keep in mind these channels are all on the same sid. Additionally I believe the connected device limit listed on the Nighthawks (30 devices I think) is probably an best case scenario number.
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). My home has approximately 25 devices (rgb bulbs, thermostats, dimmers) and it seemed like the MR60 struggled to keep all of them happy/connected in a 2000 sq foot house with normal (not concrete or metal) walls.
Given the wifi/IOT devices out there right now usually have junky antennas and poor support for anything out of the ordinary when it comes to wifi. I guess this was to be expected.
The solution (and you are probably not going to like it..) was to return my MR60 and purchase an orbi mesh system (still netgear made). Once I installed the orbi all my connected devices on both 2.4 and 5ghz could talk to each other.
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.
Probably too late to return my system, so I'd have to eat the cost. So much for thinking I was getting a "better" system than if I'd just bought a single router, rather than a mesh system. Very disappointed . Thanks for answering.
JamesterReyburg what cost? Find the App on Google Play resp. the Apple App Store, and contact the App maker. Or get in contact wth the maker of your wonderful IoT and point them to this thread resp. my post above.
Again: This is neither a Mesh/router issue nor a problem with the Android or Apple mobile. Granted, both could add controls to allow a 2.4 GHz connection - but for several practical reasons, this isn't available.
