NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
The guest network isolation is currently bad / insecure and inflexible on the Orbi family.
There should be a separate dhcp / subnet for guest network with ability to allow / disallow direct traffic between clients + specific devices (by IP/range) in Router mode.
In AP mode, simply add industry standard VLAN (ingress / egress) support for main / guest networks, so the physical L2 (wireless) layers can be completely isolated from each other and with a proper router that handles separate VLANs / IP subnets with DHCP servers on each subnet + customizable firewall between subnets, any possible configuration is possible!!! This is #1 priority in my request, even if the Router mode's guest network capabilities remain basic / limited.
In AP mode VLAN support is a very simple and easy feature to add and brings this device family to enterprise level in terms of security & flexibility!
There should be a separate dhcp / subnet for guest network with ability to allow / disallow direct traffic between clients + specific devices (by IP/range) in Router mode.
In AP mode, simply add industry standard VLAN (ingress / egress) support for main / guest networks, so the physical L2 (wireless) layers can be completely isolated from each other and with a proper router that handles separate VLANs / IP subnets with DHCP servers on each subnet + customizable firewall between subnets, any possible configuration is possible!!! This is #1 priority in my request, even if the Router mode's guest network capabilities remain basic / limited.
In AP mode VLAN support is a very simple and easy feature to add and brings this device family to enterprise level in terms of security & flexibility!
6 Comments
Same features and proper segregation is missing on the Nighthawk, the Nighthawk Pro Gaming, and the latest Nighthawk AX Series. By far not limited to Orbi and ref. VLAN to AP mode only. For advanced consumers, the current guest network "isolation" (badly leaking on the MAC level) solution is not sufficient.
The current situation is embarassing to be honest, for any serious network device provider in the market. I did not expect this at all when I ordered my Orbi. Like others, I am considering selling them on eBay and get a proper WiFi mesh.
- Everyone on this thread should go and upvote either this thread, specifically about the Orbi: https://community.netgear.com/t5/Idea-Exchange-For-Home/Next-Orbi-Firmware-must-allow-guests-to-see-each-other-but-not/idi-p/1248463 or this thread about the R8000, which is the same feature request, but for a different product: https://community.netgear.com/t5/Idea-Exchange-For-Home/R8000-Guest-Network-Needs-Separated-Wireless-Isolation-and-Local/idi-p/1050376 Both have more votes than this thread, but are asking for the same thing.
'ello. Would love this on the RBR850 Orbi...
I just noticed this is listed as a new idea, although it's 2+ years old. Can uhhhh. We get an update? Typically I wait 3 days to ask for an update, but I think it's been enough time :smileyhappy:
I have a feeling that Netgear isn't listening to feature requests, and if they did include this they would incorporate it into a new product that you have to buy vs a simple firmware update.
I agree this guest SSID VLAN tagging shouldn't be a difficult feature to add, and it is the reason I am here on the forum searching.
Probably 90% of the users of these devices have no clue what a VLAN is though and are using these things as simple NAT boxes, but even in that scenario they should have a "guest" access that is truly isolated from the non-guest network.
