NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi RBR50 router and RBS20 satellites acting like different LANs, but fine as WAN?
I have an Orbi RBR50 router and three RBS20 satellites in our home. All of them have the latest firmware. Overall, they seem to be providing my house and front and back yard with a good solid wifi...
Heck I would be happy with telling certain devices that they are not "allowed" to connect to anything other than the router. My phone for instance which is the most "mobile" (i.e. I often carry it around with me) within the house.
If I could prevent my phone from 'jumping' from the router to a satellite, that would work as a possible solution. The same with the Echo devices. If I could prevent them from accessing a different connection point so I can 'force' them to all use the same node, everything *should* work as intended. The Echo devices aren't as critical, but just a part of my observation.
For instance there is an Echo Dot in the back sunroom. If I need to reboot it for any reason, as it comes back on-line it wants to connect to the satellite in that room (of course) instead of the router. This messes up the Alexa "group". So if I need to reboot that Echo, I have to also unplug that satellite, until it completes booting up. Once it is connected to the router, (Which I can see through the admin control panel.) I can then power back up and synch that back room satellite and it maintains the "group" integrity and the Echos work as desired. The Echos don't move around the house so they don't tend to jump from node to node on their own.
Alas, the feature is part of the definition of the Guest WiFi network (only on the original RBR50/RBR20 systems):
Orbi systems have no setting to specify which of the Orbi access points can be used. Any device can connect to any access point (router or satellite) on any of the supported networks (wired, primary WiFi, Guest WiFi - IoT WiFi on some of the AX models).
There appear to be two distinct reasons to have a Guest WiFi network:
- To provide a method for transient users (i.e. "Guests") to access the network without sharing the primary network password. Once they leave, the Guest WiFi password can be changed without affecting any permanent devices.
- To provide a network for transient users that keeps them separate from the primary network. i.e. they can access the internet but not communicate with devices on the primary network.
I, personally, like the flexibility. When Uncle Ben comes to visit, I can tell him how to access the printer or how to 'cast' a program to the TV if I want to. Or, I can set the network where he cannot. It's all my choice. With the new 'separate and unequal' definition, I have to share the primary network password to let Guests do anything useful. (Boo. Hiss.)