NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAX 29 Enable VLAN WAN shuts off?
I've seen a couple posts similar that look like they fixed it but the actual solution wasn't included, or the solution wasn't what I'm looking for and would like it confirmed you cannot do this. The nighthawk just does something weird as soon as you enable the VLANs. As soon as a turn the VLANS on it's like it shuts the WAN port off.
The setup:
Internet comes into router 1.
- internal IP 192.168.254.254
- one subnet on this 192.168.254.0/24
- eth 1 runs to router 2 (nighthawk) IP 192.168.254.150 WAN
- static route 192.168.1.0/24 to 192.168.254.150
router 2 is the nighthawk RAX29.
- Like from above WAN IP is 192.168.254.150
- Internal IP 192.168.1.1
- subnet off this 192.168.1.0/24
When I just have default settings on the nighthawk (no VLANS enabled) everything is fine. to verify the static routes worked I had a PC connected to the nighthawk on 192.168.1.4 and set that as the DMZ server. I could ping and trace route from router 1 on board utilities and other devices on the 192.168.254.0/24 subnet. This worked with the nighthawk set to pull the IP dynamically through DHCP AND when I set the nighthawk settings to static.
As soon as I enable a VLAN the WAN shuts off, at least that's what it seams like. Router 1 shows the nighthawk as offline. I can't ping the 192.168.254.150 address from router 1. In the nighthawk, it looked like maybe when the VLAN is enabled it just doesn't want to use DHCP for the WAN port which is fine, so I assigned it statically and no love. Static routes don't matter from the 192.168.1.0/24 subnet at this point because the WAN port just won't respond to anything, and I was trying that in addition to assigning the static WAN info. Noting that there is the default internet vlan I created another one to test in isolation with the PC connected to the nighthawk over ethernet set to the DMZ. Nothing. I don't even want to worry about going from 192.168.1.0/24 to the other subnet. As soon as the VLAN is enabled it's like the WAN just dies. What am I doing wrong? I'm not worried about getting out to the internet. Why does this thing die as soon as I enable the VLAN feature? I haven't touched cisco command line in probably 12 years and could probably figure out how to do it on that in less time than I've already spent on this!
Why am I doing this? I can use a PI as a DHCP server and issue out IPs based on VLAN tags for IOT and home lab VLANs where things are less than ideal and I can torch the infrastructure if I need too... and since the wife works from home too I can't just flash my network equipment all willy nilly anyomore :-(.
2 Replies
- VLANs on NG routers are not full-blown VLANs as you seem to think they are. They're there or are meant for specific ISP configs. They're not "general" VLANs
What does that mean in the context of the issue I'm seeing where as soon the feature being enabled and everything else failing? Is it literally just throwing the VLAN tags on the packets and unable to do the L3 switching it's advertising? I haven't ran a PCAP yet but I'm putting 2+2 together and based on what others have been having issues with, the weird work arounds, and the non-answers with comments on how the VLANS aren't REALLY VLANS they are some special other thing being a called a VLAN it would make sense. If they aren't VLANS why is company that produces networking equipment putting that label on it knowing that it means a certain thing to an entire industry?
