NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000v2 VLAN Not Working
Hi All, Just spoken to Netgear support (the free one) not a huge help so hoping that I can get some more assistance on here before I make the annoying decision to send this device back. I hav...
Hello Charles,
craftynetworker wrote:Problem I have is with VLAN's they seem to be quite poor on these devices. The limited setup options leads me to assume that you cannot have a different IP range for your VLAN's?
There is just very limited support for some tagging on the WAN side of the Netgear consumer routers (Nightawk, Orbi, Orbi Pro) - mainly to allow the configuration of an Internet access which is operated in tagged mode. Beyond, there is no support for VLAN tagging - so no multiple VLANs on the LAN side of the router, no dedicated VLAN for the guest network (Netgear seems to be proud of their limited wireless-only guest isolation link layer technology for this purpose). Amazing that their customer service was not able to answer this.
Hello Charles,
craftynetworker wrote:Problem I have is with VLAN's they seem to be quite poor on these devices. The limited setup options leads me to assume that you cannot have a different IP range for your VLAN's?
There is just very limited support for some tagging on the WAN side of the Netgear consumer routers (Nightawk, Orbi, Orbi Pro) - mainly to allow the configuration of an Internet access which is operated in tagged mode. Beyond, there is no support for VLAN tagging - so no multiple VLANs on the LAN side of the router, no dedicated VLAN for the guest network (Netgear seems to be proud of their limited wireless-only guest isolation link layer technology for this purpose). Amazing that their customer service was not able to answer this.
Kind of what I figured.
Thanks for clarfying, got through to technical support lady who asked me what my IP was over and over and couldn't really understand why it was 192.168.79.x rather than 192.168.1.x... I knew then I was on to a lost cause :-)