The output of these commands doesn't match the article, and indeed doesn't seem to make sense.
- 3 default VLANs, 0, 1, and 2.
- Ports appearing in 2 vlans but with no tagging
- "vlan#ports" info doesn't match "port#vlan" info
- Both VLAN 1 and 2 set as default (asterisk in "vlan#ports" output)
Can someone explain this to me and how to configure the CLI to set up multiple VLAN's?
I did the hard resets as specified in the E2500 installation wiki so I don't think this is caused by a conflict with "leftover data" from the stock firmware. I did start with the V3 mini build. The router does function normally in the default configuration.
Joined: 08 May 2018 Posts: 14243 Location: Texas, USA
Posted: Wed Mar 25, 2020 14:09 Post subject:
It's because especially Broadcom 802.11n and 802.11ac devices include an invalid vlan in the defaults within the firmware code for some unexplained reason. It is of no consequence unless you actually need to use vlan0 for something else.
Does this mean I can:
- Ignore VLAN0
- Assume VLAN1 is the default internal LAN, and VLAN2 is the default WAN
- Proceed with creating VLANs designated 3 or higher per the Switched Ports article?
BTW, if you are the author of the Switched Ports article, thank you for doing that. It's very clear and helpful.
Well, I tried to create a separate VLAN3 connected to physical port 4, and it's not going so well. I couldn't get it to work. Worse, I've lost access to port 4 and don't know how to get it back. The details:
I adjusted the VLAN and port configuration per the Switched Ports article as follows:
-I unbridged vlan3, and set it with an IP 192.168.3.1/24
- Created DHCP 0 and set it to VLAN 3
After save, apply, and reboot I was able to access the router on external ports 1 - 3 at 192.168.1.1. I was not able to access it on port 4.
I tried with the network adapter set to static 192.168.1.48 and 192.168.3.48. I tried the address 192.168.1.1 and 192.168.3.1 on both of those static settings. Then I tried setting it to dynamic and the router assigned an IP to the PC that was nowhere near any of the above, with no gateway specified. I didn't write it down but it wasn't in the 192.168.x.x range.
At this point I executed the "erase nvram&&reboot" command. This returned everything to default on the above port and vlan values and on the GUI, but I still couldn't access port 4. When I plug into it and ping 192.168.1.1 I get "request timed out". If I do it on powerup I get 2 instances of TTL=100 then "request timed out". Pinging ports 1 - 3 produces TTL=64 and they otherwise work fine.
An arp -a command on port 4 shows address 192.168.1.1 present, but attempts to access it via browser fail. Attempts are successful on port 1 - 3.
30-30-30 hard resets have no effect.
I tried to revert to the mini build in hopes this would clear it. This fails using the web GUI. On TFTP it says "success" but after reboot the mega build is still there with the same problem. This is true on a load and reboot with and without doing a hard reset after the load has settled for 5 minutes.
I tried to revert to the factory firmware with TFTP but it just fails every time.
I don't think it's a hardware problem or specific to this build. I previously tried this on a WRT-320N with a different (obviously) build, and the same thing happened. In that case I was able to revert to the stock firmware and the problem went away.