NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Split WiFi Networks
Hello, I just purchased the Nighthawk MR60 Mesh WiFi 6 system. I have a couple of indoor cameras that only work on 2.4 GHz, but they are able to connect to a 5 GHz network, so merged networks don...
Hello unimatrixjohnny,
Welcome to the community! The MR60 Mesh System currently does not support this feature. However, this would be a great suggestion to be added in our Idea Exchange Board for new ideas to possibly be implemented in the future.
https://community.netgear.com/t5/Idea-Exchange-For-Home/idb-p/idea-exchange-for-home
Christian
One more of these odd questions...
unimatrixjohnny wrote:I have a couple of indoor cameras that only work on 2.4 GHz, but they are able to connect to a 5 GHz network, so merged networks don't work with them.
Sorry please? A 2.4GHz-only client can only connect to a 2.4 GHz radio - not the the 5 GHz radio. It does not matter if the same SSID is used on both the 2.4 GHz and 5 GHz radios (on the router and all satellites). There is no "2.4 GHz" and no "5 GHz" network. All the radio interfaces and the Ethernet ports connect to the very same network - - everything does connect to the same layer 2 and layer 3 network.
Here again, for the first time in the 802.11 WiFi standards, with 802.11ax (WiFi 6) we have a design which is NOT designed for peak single client performance, but much more for enhanced concurrent usage. The MR60/Ms60 we talk of here does inherit by far not the fastest WiFi 6 technology available, otherwise the low cost would not be possible. The key features are coverage and availability without much effort - no single client speed wonders. Taking the fact that most installations will have much more older standard wireless clients, even lower-end spec'ed WiFi 6, makes the MK62 (or MK63) kit a nice player.
Not having 802.11k RRM (Smart Connect) in place will lead to sticky clients: They won't change away from the "poor-but-long-reach" 2.4 GHz unless the signal and quality will go submerging - this will hit especially clients roaming into the coverage area of the network. That's certainly not what you are behind, too.
This is why all newer 802.11ac and WiFi 6 extender implementations make use of 802.11k RRM, too.
If there are to many clients falling over to 2.4 GHz, the mesh should be resized to a more dense set-up.
In my opinion, there is no reason for not operating anything from a single router with two (or three) radios, a small mesh, and up to large scale event location, hospitality, or enterprise class WiFi installations without 802.11k RRM aka. Smart Connect.
And no, I'm not Netgear - and known for not holding back with criticism where valid. I fully disagree: Spliting SSID and killing Smart Connect would be a very bad solution!!!
That is 100% false. There are many devices that include dual band adapters but only function over a single band. Please don't provide poor advice like this to people.
Splitting the bands is absolutely necessary in many network applications.
Splitting the bands is absolutely necessary in many network applications.
unimatrixjohnny wrote:
There are many devices that include dual band adapters but only function over a single band.This is a bad device then, typical IoT crap. Why should a WiFi client connect to the 5 GHz network - but not work ?!?
Provide examples please - "many" is simply useless.
- I'm not here to educate you lol. There are many multi thousand dollar pieces of agricultural equipment that is this same way, many wireless home backup power supplies and home security systems that all function this way. It's cheaper to buy dual band wireless adapters than single band. The programming of the software/firmware is what determines the bands that it can function over, and there are many applications where connecting to a 5GHz band would be detrimental to the functionality of the equipment. Thanks for not helping at all by not knowing networking/programming at all.
Yea, you got it exactly right - poor to awful programming would be exactly that: Complain to the IoT vendor, talk to your lawyer (product not fit for purpose!), or put the crap into the trash bin if they are unwilling to fix it. Not a problem to be resolved by forcing a crappy set-up.
If I don't want a dual-band WiFi client to connect to the 5 GHz network - the client developer has to disable the 5 GHz interface. That much about programming.
Note: There are not many dual-band WiFi devices have such a control e.g. to disable the 5 GHz (or for the same alternate the 2.4 GHz) as it's simply not required in reality.
Some community members started to collect a list of non-WiFi-compliant devices and/or et-up procedures ("connect oyur mobile to the 2.4 GHz nonsense...") in the Orbi community section ... I know it's not very long yet.
It's a good behavior to name these products in the public - not a question of educating me...