Posted: Tue Mar 19, 2024 3:05 Post subject: [Solved] Netgear R6400v2 and VLANs [Not working]
So after a few days messing with my ancient WRT54GLs, in an attempt to set up a 2.4ghz WAP/VAP for IoT and VLANs, I gave up because they kept erasing the settings on boot and I got terribly frustrated and threw them in the fscking trash can. So I found a NG6400v2 at a thrift shop for $15. Happy!
I flashed DD-WRT r53562 on it. I was pleased the see the GUI was pretty much identical to my R7800 (which is used only as a WAP/VAP) and used it for a guide to set this one up since they will be so far apart they should never see each others radios.
I then set up the WAPs/VAPs, then the bridges br1-br3) then the VLANs via the Switch Config page. VLAN10-12 and assigned them all to only switch port 4. Tagged them all on port 4 (while still including vlan1) and the CPU port 5 then added them to the bridges as well as the 2.4ghz wireless VAPs. Rebooted and the router is not accessible from port 4. The other ports work fine so I am not locked out.
I am guessing I may still need to use the Switched Ports Wiki ( https://wiki.dd-wrt.com/wiki/index.php/Switched_Ports ) because this should not be happening if the Switch Config tab is working correctly for this router, or am I wrong about that?
"swconfig dev switch0 show" shows the vlans correctly configured for the right ports.
But using the nvram show | grep port.*vlans | sort command, the vlans10-12 do not show up and I would think they should. They are also not assigned to et0. Do they need to be?
I am writing this asking if anyone else has ran into this issue on this particular router? I can post screen shots and additional shell outputs if needed, just don't have the time at the moment. _________________ Linksys EA8500 (Internet Gateway, AP/VAP) - DD-WRT r53562
Features in use: WDS-AP, Multiple VLANs, Samba, WireGuard, Entware: mqtt, mlocate
Wireless 5ghz only
Netgear R7800 (WDS-AP, WAP, VAP) - DD-WRT r55779
Features in use: multiple VLANs over single trunk port
Linksys EA8500 WDS Station x2 - DD-WRT r55799
Netgear R6400v2 WAP, VAP 2.4ghz only w/VLANs over single trunk port. DD-WRT r55779
OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.
Forum member #248
Last edited by lexridge on Wed Mar 20, 2024 2:47; edited 1 time in total
alright, just dicovered this... I can connect the router's VAPs and get an IP address from the main router on every VAP (all different subnets). I have verified by the IP addresses assigned to my phone when connecting. So the wireless VAPs w/vlans are working. I just cannot access the router from its own IP address via port 4, yet apparently the main router with multiple DHCP servers can see all the address except for the main IP address. WTH?
The following pic I am plugged into port 3 as port 4 is not accessible.
Selection_001.png
Description:
Filesize:
35.35 KB
Viewed:
669 Time(s)
_________________ Linksys EA8500 (Internet Gateway, AP/VAP) - DD-WRT r53562
Features in use: WDS-AP, Multiple VLANs, Samba, WireGuard, Entware: mqtt, mlocate
Wireless 5ghz only
Netgear R7800 (WDS-AP, WAP, VAP) - DD-WRT r55779
Features in use: multiple VLANs over single trunk port
Linksys EA8500 WDS Station x2 - DD-WRT r55799
Netgear R6400v2 WAP, VAP 2.4ghz only w/VLANs over single trunk port. DD-WRT r55779
OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.
And what am I supposed to do with the half-complete information?
Post full screenshots of the "networking" tab
Post the configuration of the gateway (a trunk configuration is not a one-way configuration but requires correct settings on both sides)
Quote:
I am guessing I may still need to use the Switched Ports Wiki
nobody cares about outdated stuff
Quote:
The following pic I am plugged into port 3 as port 4 is not accessible.
this raises some questions....
You plugged the trunk cable into port 3 and now you have access to VLAN1?
Then your trunk is configured incorrectly on the gateway and VLAN1 is not tagged.
Or do you have a PC/client connected to port 3?
Since port 4 is tagged, you can only connect devices that are capable of VLAN tagging to this port.
Mostly true, except for very old routers such as the WRT54GLv1.1 (no swconfig command). I tried getting this to work on two of them, and actually DID make it work. But upon reboot, all NVRAM settings would reset to factory. Tried on two different WRT54GLs across several DD-WRT releases, going back to 2021.
Quote:
this raises some questions....
You plugged the trunk cable into port 3 and now you have access to VLAN1?
Then your trunk is configured incorrectly on the gateway and VLAN1 is not tagged.
Or do you have a PC/client connected to port 3?
Since port 4 is tagged, you can only connect devices that are capable of VLAN tagging to this port.
however post complete information
this can only be a vlan1 problem if everything else works
You confirmed exactly what I suspected, since vlans 10 11 12 were all working but the router was not accessible via the port4 on its own IP. I dug into it more closely this morning. My setup is rather complicated, but is temporary since the R6400v2 will be moved to a different location once configured.
Port 4 of the EA8500 Gateway (tagged vlans 1 10 11 12) comes to my external garage and connects to a managed switch, a TP-Link TL-SG108E. Switch ports 1 2 6 7 are all tagged to match the Gateway. Port 7 is plugged into port 10 of a Dell PowerConnect 2824 managed switch. My test environment is plugged into port 24 of the Dell switch to port 4 of R6400v2. So, this was the problem. The Dell switch does not allow vlan 1 to be tagged, but did allow vlans 10-12 to be tagged.
So bypassing the Dell switch and going directly into the TP-Link switch fixed the problem. So I now know I will not have this issue once I move this R6400v2 back into the house directly connected to the Gateway.
I guess if I want to continuing using this Dell switch, I am going to have to move DDWRT vlan1 to another vlan....EVERYWHERE (across 5 managed switches and 4 routers). It is odd this setup worked on the WRT54GLs (until rebooting). Old hardware perhaps not caring to check for tags perhaps. Who knows.
Thank you ho1Aetoo! All good now. _________________ Linksys EA8500 (Internet Gateway, AP/VAP) - DD-WRT r53562
Features in use: WDS-AP, Multiple VLANs, Samba, WireGuard, Entware: mqtt, mlocate
Wireless 5ghz only
Netgear R7800 (WDS-AP, WAP, VAP) - DD-WRT r55779
Features in use: multiple VLANs over single trunk port
Linksys EA8500 WDS Station x2 - DD-WRT r55799
Netgear R6400v2 WAP, VAP 2.4ghz only w/VLANs over single trunk port. DD-WRT r55779
OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.
Perhaps so. I didn't buy it fortunately. It was given to me a few months back. I will dig into it a little more and see if there is a way to tag vlan1, but I have my doubts. _________________ Linksys EA8500 (Internet Gateway, AP/VAP) - DD-WRT r53562
Features in use: WDS-AP, Multiple VLANs, Samba, WireGuard, Entware: mqtt, mlocate
Wireless 5ghz only
Netgear R7800 (WDS-AP, WAP, VAP) - DD-WRT r55779
Features in use: multiple VLANs over single trunk port
Linksys EA8500 WDS Station x2 - DD-WRT r55799
Netgear R6400v2 WAP, VAP 2.4ghz only w/VLANs over single trunk port. DD-WRT r55779
OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.
Well Dell really did screw that up. After a bit of searching, vlan1 is not allowed to be tagged. Only 2-4096 can be tagged. Whoever thought of this was a dumb***! _________________ Linksys EA8500 (Internet Gateway, AP/VAP) - DD-WRT r53562
Features in use: WDS-AP, Multiple VLANs, Samba, WireGuard, Entware: mqtt, mlocate
Wireless 5ghz only
Netgear R7800 (WDS-AP, WAP, VAP) - DD-WRT r55779
Features in use: multiple VLANs over single trunk port
Linksys EA8500 WDS Station x2 - DD-WRT r55799
Netgear R6400v2 WAP, VAP 2.4ghz only w/VLANs over single trunk port. DD-WRT r55779
OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.
