NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SEPERATE PASSWORDS FOR 2.4 and 5
Running a new SimpliSafe doorbell and it keeps dropping offline. Technician says it needs to be on 2.4 specifically and seperate passwords would help. Is this possible on this system? Thanks in adva...
No. Orbi doesn't support splitting of the SSID or PWs. If the device only supports 2.4Ghz, then it will never see or use 5ghz. This is not a 5Ghz issue.
What Firmware is currently loaded?
What is the Mfr and model# of the ISP modem the NG router is connected too?
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials when wirelessly connected.
What channels are you using? Auto? Try setting manual channel 1 on 2.4Ghz.
Any Wifi Neighbors near by? If so, how many?
Try enabling Beamforming and MIMO(MIMO may or maynot be needed) and WMM. Under Advanced Tab/Advanced Settings/Wireless Settings
Try disabling the following and see:
Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s).
Actually this is a 5ghz issue. If the phone or tablet is on 5ghz then some 2.4ghz devices cannot be set up. It's a very common issue where both the phone and device being setup must be on the same band. Getting off the 5ghz band temporarily is the fix.
No this is a IoT device Mfr software setup issue. There setup software limits or seems to require the setup mobile device to be connected to the 2.4Ghz radio. Mfrs forget that most mobile devices are dual band supporting devices. Thus the mobile devices prefer 5Ghz over 2.4Ghz and the Mfrs forget that 2.4 and 5ghz are on the SAME network. So if IoT Mfrs would take this into account and let there setup software work on 5Ghz for the setup mobile device, all this woudn't be a problem.
Thanks to NG for helping these users out thought:https://community.netgear.com/t5/Orbi/orbi-20-cannot-connect-Swann-Camera/m-p/1822441/highlight/true#M75389
https://community.netgear.com/t5/Orbi/Kindle-Paperwhite-not-found-my-Orbi-RBR40/m-p/1712069/highlight/true#M53584
Jetdrive wrote:Actually this is a 5ghz issue. If the phone or tablet is on 5ghz then some 2.4ghz devices cannot be set up. It's a very common issue where both the phone and device being setup must be on the same band. Getting off the 5ghz band temporarily is the fix.
Like I said the fix is to reduce or eliminate the 5ghz signal during setup of some 2.4ghz devices. Your are right to blame the manufacturers of the devices; however, the work-around to set up the device has to do with the 5ghz signal which you said was not a an issue.
All we can do is complain to the manufacturers but that won't provide a quick fix as we all know from using Netgear products.
Don't listen to Furrie. Everytime this is asked he keeps claiming its not possible even though its well known and documented that you can do it.
Go here and follow the steps. A lot of IOT devices require seperate SSID to work and don't support band steering.
dan801 wrote:Everytime this is asked he keeps claiming its not possible even though its well known and documented that you can do it.
It's neither supported nor endorsed by Netgear. And the results and effects vary with the Orbi models and firmware releases - and might change again following a reboot. That's why some senior community members don't believe in such a "solution". Yes, FURRYe38 - count me in here, too.
dan801 wrote:A lot of IOT devices require seperate SSID to work ...
Nope. Some crappy IoT require the discovery App to be run on 2.4 GHz for discovery of the 2.4 GHz IoC. At run-time, once configured, there is no such requirement.
A 2.4. GHz IoT will never connect to a 5 GHz AP because it can't see it at all - so it does not care about it.
The IoT devices should be configured to the "primary" and long-term single SSID - and not to a temporary "split" SSID config name.
dan801 wrote:A lot of IOT devices ... and don't support band steering.
An AP with band steering will delay the association of a 2.4GHz client connection attempt awaiting another connection attempt on 5 GHz. If this does not happen, the 2.4GHz association will be allowed. What should the IoT not support now here? It does not recognize that the AP does any band steering - just the initial connection takes slightly longer.
And to round it up: Basic wireless clients as in place on many IoT don't care about neighbouring AP information coming over air from advanced APs (this is what the consumer wireless industry does understand under "Mesh" support). What can happen after a power failure? The primary AP (the Orbi router) can come up before the satellites do, so a "dumb" IoT will connect to the router - and stick - to that connection, even if a much better signal will come from on-air from the satellite after some delay. Lack of "Mesh" support, it will not learn about the neighbouring APs - and stick with the poor signal forever.
Now we come back to the subject SimplySafe devices: Start reading here: https://simplisafe.com/forum/customer-support-forum/installing-and-using-simplisafe/simplicam-losing-connection - thier community is full with connection loss, separating 2.4 and 5 GHz does not cure, some have issues with some specific AT&T routers, others report that changing to Orbi fixed the Simplysafe device disconnection problems. Funny, isn't it?
And then once more, please explain the interested reader why a configured wireless IoT (say one of these Simplysafe cameras and doorbells) which have "lost" the connection does not automatically re-connect to the wireless, and then to the cloud? That's very unlikely because of the 2.4 GHz wireless (again the only band the IoT does see and know about) has the same name like the 5 GHz ....
So Navyav8r please share this information with the Simplysafe support engineer. I'm happy to read about thier explanation attempt.All my IoTs work with a single SSID name and PW. Zero need to separate SSID. Orbi works with IoTs as designed.
I say that it's NOT supported by NG!!
Again, this is a IoT Mfr issue and not a NG issue. For users who want there IoTs to work with Orbi, Just follow this simpler method and you'll be fine.
https://community.netgear.com/t5/Orbi/orbi-20-cannot-connect-Swann-Camera/m-p/1822441/highlight/true#M75389
https://community.netgear.com/t5/Orbi/Kindle-Paperwhite-not-found-my-Orbi-RBR40/m-p/1712069/highlight/true#M53584IoTs don't require separate SSIDs. 2.4Ghz only supporting IoTs don't even care or even SEE 5Ghz signals in the first place, so why would there be a need for a requirement or support band steering. It's not up to these device to bandsteer in the first place. The router does this. dual band devices may bandsteer since they have the ability to pick and choose which freqency to connect to since these dual band devices support both frequencies which are not seen on 2.4Ghz only IoT.
You don't have to listen to me either. :smileywink:
Good Luck. :heart:
dan801 wrote:Don't listen to Furrie. Everytime this is asked he keeps claiming its not possible even though its well known and documented that you can do it.
Go here and follow the steps. A lot of IOT devices require seperate SSID to work and don't support band steering.
- At the end of the day you and crimpon dribble your spew and tow the netgear line. Saying that it’s not possible is an outright lie. Someone asking a question on how to do it should be able to make up their own mind. Quick search shows that same question has been asked 183 with plenty of requests in the request section for the ability straight through the UI. Plenty of people are having issues with band steering and your posts do not help them.
dan801 wrote:
A lot of IOT devices require seperate SSID to work and don't support band steering.
That's an interesting observation. I have never seen anyone suggesting that here before now.
Can you provide us with a link to a definitive.
Like everyone else, I run a bunch of IoT stuff that happily runs on a wifi network with the same SSID for 2.5 and 5 GHz, but I am willing to read any evidence to the contrary.
In the last, people have had a lot of success by temporarily disabling the 5 GHz SSID so that the set up process can work. But there may well be some devices that are even worse than those that insist on 2.4 GHz during setup. It would be good to know which devices they might be.
I'm on the same page as michaelkenward . When I look for products, there are almost always alternatives at similar prices. I would appreciate knowing which are not going to work on my Orbi system so that I can avoid purchasing them.
