NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Guest Network in AP Mode still works like a router
I have my AX5700 (RBR840) with 2 satellites set-up in AP Mode. I have Firewalla Gold router set-up to manage the network. For some reason the Orbi Guest Network is still operating in Router Mode an...
If its a 192.168.2.x address for Guest Network, most likely intended by NG and by design. Thats the default subnet for all Guest Networks.
Thanks, but I do not understand. In AP Mode, the Orbi should not assign any IP addresses, all of that should be handled by the stand alone router. It is only the Guest Network that is assigning IP's, the Main Network is getting IP's from the stand alone router(?)
Not for Guest Network. NG I believe chooses to keep the Guest Network subnet away from the main LAN while in router mode or AP mode for security reason and isolation.
I agree with FURRYe38 . The nature of the Guest WiFi network has changed over the years. My understanding is that there are two fundamental reasons to have a Guest network:
- To have a network that is "walled off" from the primary network. Devices on the Guest network cannot reach the primary network.
- To have a network that is easy to share without compromising the password of the primary network. Often the Guest network password is simple to enter and since none of the primary devices are using it, the Guest network password can be changed at any time without disturbing the primary network. (The thought of reconfiguring dozens of WiFi devices with a new password can be overwhelming.)
The original Orbi product (2016) had it both ways. The network could be configured to keep devices on the Guest network separate or to allow them to interact with the primary network. I thought this was an ideal solution. Suppose family or friends come over and one of them says, "Can I print something out?" No problem. Just switch the option to "Enable" and tell them how to access the printer. When they leave, disable the connection (or change the Guest password). No impact on the primary network at all.
Unfortunately (in my opinion) the folks at Netgear went "all in" on the first concept: keep devices off the primary network.
Whereas the original Orbi had only one IP LAN Subnet, the AX product line places the Guest network in a separate IP subnet that cannot interact with the primary network.
If you want Guest devices to be separate from the primary network, then the Orbi assigning them IPs in a separate network should be "no problem". These are "Guest" deivices. They come and go. Who cares what IP address they have for the brief time they are on the network?
Thanks. I understand the logic of this.
However, here are the three problems this gives me:
1. In AP Mode, the Orbi hides the Access Control and Network Settings page, I lose total control of my network and if someone is on my network that should not be there, I cannot block them. I have no idea what security protocols are setup (if any other than WAP and a password) on the Guest Network.
2. Many smart home devices can only connect to a 2.4G network, they cannot connect to a mixed 2.4/5G network. I had set-up those devices on the Guest Network which I have restricted to 2.4G. However, now these devices cannot interconnect. For example, my Matter hub is on the 5g Main Network, it can not control the Matter devices on the 2.4g network.
3. My main router is a Firewalla Gold which manages traffic in a secure way. I am concerned that everything on the Guest Network is now bypassing that or, at the very least, is aggregated in a "single device" and I have no idea of what device is generating what flow.
I replaced an older Orbi set up with this one (that worked in the maker you described for older systems) and would like to find a way to solve these problems.
Thanks,
Pat
