NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
unimatrixjohnny
Feb 28, 2020Tutor
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't work with them. Is there a way to split the WiFi networks? There's nothing in the app or the admin portal that shows they can be split. Is there any way to do this on these devices?
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
10 Replies
- Christian_RNETGEAR Employee Retired
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
- schumakuGuru - Experienced User
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.- schumakuGuru - Experienced User
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.
- davel4waTutor
I have expressed the same concern about devices that I have that operate only on 2.4GHz wifi band. As expressed here devices that operate only on 2.4GHz will only connect in that band. The rub is that I have one device that sets up through an Android app and that app requires that the app platform be connected to the 2.4GHz wifi band. Luckily the app has an alternative method to connect and setup the device which works. That being said it is possible, I have now found, using the web page interface to the router, to disable either or both 2.4 and 5GHz radios in the 'Advanced Settings/Wireless settings menu. This should allow you to deal with your 2.4GHz devices setup and you can reenable the 5GHz band once you are done.
MR60 Nighthawk Mesh Wifi Router
- davel4waTutor
In regard to my previous post, the switches on the MR60 router 'Advanced Setup/Wireless Settings' do NOT turn off the wireless radios but simply select whether or not the SSID is broadcast which is sort of senseless as both radios have the same SSID.
The alternative to dealing with 2.4GHz only devices for me, was to use my TPLink wifi extender which only supports the 2.4GHz band. By connecting my phone wifi to the extender it is possible to set up those devices which require the 2.4GHz band.
Nighthawk MK62 Mesh router
- schumakuGuru - Experienced User
davel4wa wrote:
I have that operate only on 2.4GHz wifi band. As expressed here devices that operate only on 2.4GHz will only connect in that band. As expressed here devices that operate only on 2.4GHz will only connect in that band.
A device with a 2.4 GHz client only, will always only connect to the 2.4 GHz band for the obvious reason. Nothing is stopping this. The presence of what ever other wireless or wired connection layers is not relevant: These devices simply wont care!
davel4wa wrote:
The rub is that I have one device that sets up through an Android app and that app requires that the app platform be connected to the 2.4GHz wifi band.
Talk to the vendor of this Po* - the discovery might initially using some local WiFi connection from the mobile to the device itself, then configure the SSIDs and security, then discover again using some L3 and up protocol. Changing their discovery Apps for not checking a 2.4 GHz connection is established, or to allow to continue regardless would be a snap. Have just set-up an Arlo camera with 2.4 GHz only these days - the App asked to connect to the 2.4 GHz WiFi, said OK, continue, ...knowing the mobile is on the 5 GHz ... the discovery and the set-up went through completely seamless. Gee, on the network there is no difference, regardless if the device is connected on 2.4, 5, 60 GHz, Ethernet, Fast Ethernet, Gigabit Ethernet, 10G Ethernet, 40G Ethernet, ...
Love to hear the idea of using an alternate WiFi router using the same SSID and security on the 2.4 GHz band made the configuration of the same device settings possible. Some IoT makers seem to even check the MAC - so the device won't associate with the Mesh WiFi later - so this does not always work.