NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
How t o distinguish 5G and 2G channels on Orbi?
Hi there. I just installed the system and it seeems to be working normally. I see only one WIFI network name however and can't distinguish 5G and 2G channels. This is important to me since I have some devices that run 2G only (security cameras). Any ideas? Thanks.
Rick
Another easy way to help your 2.4Ghz only devcies to connnect or setup with Orbi, you can uncheck the "Enable 5G SSID broadcast" check box temporarily, then save settings. This keeps any 5Ghz supporting devcie from connecting to the 5Ghz radio. Then you should be able to use the setup mobile device to get your 2.4Ghz device connected to Orbi. When your done, you can check the "Enable 5G SSID broadcast" check box to re-enable the 5Ghz SSID for you other devices.
rickbo wrote:Thanks very much. For set-up, my security cameras require that my phone (app) be connected to the same 2.4G network as the camera. So I need to force my phone to 2.4. With previous routers it was simple since there were distinct SSIDs. Wish me luck.
10 Replies
Devices that have no 5G radio cannot detect 5G signals. For them, 5G does not exist.
When these cameras are told to connect to the Orbi WiFi name (SSID) using the password, they will connect to the 2.4G channel because that is the only channel they can find.
Hi,
There is an unofficial way to split the 5GHZ and 2.4 GHZ SSIDs:
CheerZ and goodluck :)
Thanks very much. For set-up, my security cameras require that my phone (app) be connected to the same 2.4G network as the camera. So I need to force my phone to 2.4. With previous routers it was simple since there were distinct SSIDs. Wish me luck.
Complain to the security camera maker - all the 5 GHz, 2.4 GHz, and LAN ports connect to the very same layer 2 network - everything is fully transparent, including IP broadcast, multicast, ... This is definitively neither a problem Netgear or your phone maker has to resolve. Why on earth should a wireless client need options to connect to 2.4 GHz only? There is no reason for this...
Some crappy consumer routers (inlcuding some older Netgear units) have problems with certain protocols passing to all the interfaces [e.g. some kind of Multicast traffic] properly. That's why some IoT makers state it has to be on the same 2.4 GHz network.
