NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Feature request (force a device to a specific Orbi)
I have one problem device that, for some reason, always chooses the Satellite Orbi instead of the Router Orbi, which is always the furtherest away from the device. The Router Orbi is by far the closer one to the device. I can reboot the network and the device will connect to the Router, but will eventually creep back to the Satellite for whatever reason. It's a stationary device (TV) and never moves. I'd like to request to have a feature implemented that will allow us to "force" or designate a specific device to a specific Orbi. I know they plan on releasing a firmware that will allow us to customize how the lights on top act (always on, etc), which I hope gets released soon! Also, a Guest Network feature would rock!
13 Replies
hi namdnas
i doubt there is a way to force clients to stay on one transmission unless they run some form of black list per transmission which is more seen on commercial ap's etc
i also doubt they way the lights work will be changed ether as the dev team has spent a lot of time on how the lights perform and as far as i understand there are no plans to change this at this time
pete
i would like to have this feature too. i have security cameras that never move and for some reason i have 1 that insists on connecting to the router when the satellite is literally 10' away. please make a way for us to assign certain devices to either the satellite or router!
Let me chime on here too. I played around with UniFi APs and they provided this feature. Loved it because some times it makes sense to connect to the other device.
At a minimum, I'd like to see a feature so clients cannot connect to Orbi until the Satellites are ready to go. Often after a reboot, power outage, firmware upgrade, etc.. the router comes up first and many clients latch onto it and never let go. If clients were prevented from connecting until the Satellites were up, then the clients would latch on to the closest unit.
djc6 wrote:At a minimum, I'd like to see a feature so clients cannot connect to Orbi until the Satellites are ready to go. Often after a reboot, power outage, firmware upgrade, etc.. the router comes up first and many clients latch onto it and never let go. If clients were prevented from connecting until the Satellites were up, then the clients would latch on to the closest unit.
Problem with that is if the sat connects first it can't get internet connectivity. Then your devices would complain. Besides you can always disconnect/reconnect to the SSID and the client device usually connects to the strongest signal.
whsbuss-1 wrote:
Problem with that is if the sat connects first it can't get internet connectivity. Then your devices would complain. Besides you can always disconnect/reconnect to the SSID and the client device usually connects to the strongest signal.I don't follow what you are saying. My suggestion is that clients are prevented from connecting until the satellites are connected to router - so how would the clients complain. Also what would prevent the satellites from internet connectivity.
I don't want to run around the house and disconnect/connect 20 devices every time I do a firmware upgrade so that the clients are connected to the optimal BSSID. Right now there is a race condition in that the router is available to the clients before the satellites are.
