and this is R2 on the other side of the house, in the garage. _________________ 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.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Sun Aug 01, 2021 23:46 Post subject:
lexridge wrote:
kernel-panic69 wrote:
brctl show will show what's what via ssh / telnet. Limited picture here, though. One snippet of a screen shot to go by. Is vlan10 set to 'default' or 'unbridged'? Incomplete information doesn't help resolve things, does it?
brctl does show the correct bridging. So the GUI is lying to me.
Code:
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.149182673476 no vlan1
wlan0
wlan1
br1 8000.149182673476 no wlan0.1
Both vlan10 and wl0.1 are default. The IP is set in br1.
It is not showing correctly, where's vlan10 on br1 from output of brctl? All it shows it wlan0.1 ... only thing I can say is try adding it manually. You may even have to add it to your startup script if it isn't persistent.
brctl show will show what's what via ssh / telnet. Limited picture here, though. One snippet of a screen shot to go by. Is vlan10 set to 'default' or 'unbridged'? Incomplete information doesn't help resolve things, does it?
brctl does show the correct bridging. So the GUI is lying to me.
Code:
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.149182673476 no vlan1
wlan0
wlan1
br1 8000.149182673476 no wlan0.1
Both vlan10 and wl0.1 are default. The IP is set in br1.
It is not showing correctly, where's vlan10 on br1 from output of brctl? All it shows it wlan0.1 ... only thing I can say is try adding it manually. You may even have to add it to your startup script if it isn't persistent.
WTH, it was there. I didn't notice it was not after a reboot and my copy/paste. This is crazy.
I do add it manually with this startup:
Code:
#vlans
swconfig dev eth0 vlan 1 set ports "0t 1 2 3 4t"
swconfig dev eth0 vlan 2 set ports "0t 5"
swconfig dev eth0 vlan 10 set ports "0t 4t"
swconfig dev eth0 set enable_vlan 10
swconfig dev eth0 set apply
vconfig add eth0 10
ifconfig vlan10 up
I reboot the router, and it's there, but after 25-30 minutes or so it disappears.
EDIT: This morning after a fresh reboot:
Code:
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.149182673476 no vlan1
wlan0
wlan1
br1 8000.149182673476 no vlan10
wlan0.1
It returns _________________ 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.
@mrjcd Yes, I have used your page many times. Thank you for making it. I think most of my confusion at this point is between tagging and trunking. When I set up tagged trunks on my switches, only one subnet seems to make it thru. It's driving me absolutely crazy!
Also @mrjcd, I should point out that your webpage shows breaking out the vlans onto individual ports. In my situation, I need all the vlans on a single trunk cable to transverse multiple managed switches, and this is only the start. In total, I will need 3 vlans all on that same cable at some point. So in the end I want a vlan for IoT, Media and Guest. While I do have a guest network presently, it is done with routing and iptables, not vlans. _________________ 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.
You should not need to have an IP configured for vlan10 nor wl0.1. That was my issue with an older build. Once I removed that on the AP, it worked. _________________ Linksys: Several WRTxx00AC variations | Netgear: 4x WNDR4500v2, 7x WNDR4300, R6400v1 | Asus: 2x RT-AC66U | Gl.inet: 3x GL-AR150
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Mon Aug 02, 2021 19:44 Post subject:
IP address should only be assigned to the bridge, same as it would be for br0. Then your dhcp server should be listening on the (new) bridge interface as it would normally be. OR on another device on the same subnet. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Okay, I have made some good progress here. I added a dual ethernet card to my main computer to better assist in testing. This allows me to get the R2 out of the testing for now and concentrate on the managed switches and their vlan assignments.
I created a vlan10 with PVID 10 on the switch port this ethernet card is plugged into (S3/P2) and tagged the port. I did the same for S3/P1 which is a trunk port to S2/P2. Then again, did the same on S2/P1,P2 and S1/P1,P2. I also tagged all these ports with both vlan1 and vlan10.
My computer DOES get a dhcp address now from R1/br1. Odd thing, I still cannot ping 10.1.0.1 (R1/br1) from the PC nor from the router to the PC (10.1.0.192). Seems odd that I can receive a dhcp address from a dhcp server that I cannot ping, but I did verify the MAC address on the router, and it did indeed send it.
I would not think I need a route, otherwise the dhcp handout should not have worked. What am I missing? _________________ 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.
I am adding my setup for clarity. The screenshots are long, I know.
Black background is the router
White background is the AP
Both are WRT3200ACM running r46750.
The VLANs are configured in the startup section. On the router, there are also a few IP table lines that allow clients to obtain an IP address on the otherwise isolated guest and VPN network.
Only the bridging section has been modified on the AP. No changes in Port Setup or DHCPD. All of the relevant changes are only present in the router's setup. _________________ Linksys: Several WRTxx00AC variations | Netgear: 4x WNDR4500v2, 7x WNDR4300, R6400v1 | Asus: 2x RT-AC66U | Gl.inet: 3x GL-AR150
That's interesting, because if I attempt to set my br1 on R2 (WAP) to all balls (ie 0.0.0.0/0) it rejects it with "IP Address value is out of range [1 - 223].".
The R2 (R6250) also is acting very strange. I combine vlan1 and vlan10 to trunk on port4 so I can use a single cable, yet it causes a network loop at the switch, WITH ONE CABLE?!?!? How can that even be possible?
Something else that I figured out too, is that if I reboot R1 (EA8500) I must go to the Network page and re-apply it to get br1 to add vlan10 with wl0.1. I am on r47097 on both routers. _________________ 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.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Mon Aug 02, 2021 23:00 Post subject:
You set your subnet-specific IP address that will apply to vlan10 and wlan0.1 on br1, NOT ON vlan10 or wlan0.1. And the IP address cannot be quad zero. I think you should probably reset the router(s) and start over. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
That's interesting, because if I attempt to set my br1 on R2 (WAP) to all balls (ie 0.0.0.0/0) it rejects it with "IP Address value is out of range [1 - 223].".
Maybe you need to reset the router and just not fill out the section when you recreate the config?
lexridge wrote:
The R2 (R6250) also is acting very strange. I combine vlan1 and vlan10 to trunk on port4 so I can use a single cable, yet it causes a network loop at the switch, WITH ONE CABLE?!?!? How can that even be possible?
Sounds like you have something misconfigured either on the switch or the VLAN config on the AP. I only have one cable connected to the AP, and the tagging is working fine.
lexridge wrote:
Something else that I figured out too, is that if I reboot R1 (EA8500) I must go to the Network page and re-apply it to get br1 to add vlan10 with wl0.1. I am on r47097 on both routers.
Do you have the "brctl addif br1 vlan10" statement in your startup config? If not, then you should ensure you add it there. _________________ Linksys: Several WRTxx00AC variations | Netgear: 4x WNDR4500v2, 7x WNDR4300, R6400v1 | Asus: 2x RT-AC66U | Gl.inet: 3x GL-AR150
That's interesting, because if I attempt to set my br1 on R2 (WAP) to all balls (ie 0.0.0.0/0) it rejects it with "IP Address value is out of range [1 - 223].".
Maybe you need to reset the router and just not fill out the section when you recreate the config?
lexridge wrote:
The R2 (R6250) also is acting very strange. I combine vlan1 and vlan10 to trunk on port4 so I can use a single cable, yet it causes a network loop at the switch, WITH ONE CABLE?!?!? How can that even be possible?
Sounds like you have something misconfigured either on the switch or the VLAN config on the AP. I only have one cable connected to the AP, and the tagging is working fine.
lexridge wrote:
Something else that I figured out too, is that if I reboot R1 (EA8500) I must go to the Network page and re-apply it to get br1 to add vlan10 with wl0.1. I am on r47097 on both routers.
Do you have the "brctl addif br1 vlan10" statement in your startup config? If not, then you should ensure you add it there.
I added brctl addif br1 vlan10 to the startup and that may have fixed that problem.
You may be right. If I untag VLAN10 on the switch, the loop stops. Just not sure why at the moment. Why would tagging it cause a network loop? _________________ 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.
Maybe you need to reset the router and just not fill out the section when you recreate the config?
I was able to set br1 on R2 to 0.0.0.0/0 via the nvram vars. Still didn't make any difference however, but could be a switch issue still. So your bridge is getting its IP address via dhcp? This doesn't make a lot of sense to me as to how this works. _________________ 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.
Joined: 13 Aug 2013 Posts: 6867 Location: Romerike, Norway
Posted: Tue Aug 03, 2021 12:53 Post subject:
The IP addresses on br1 must be set statically. Otherwise the dhcp server will not know what addresses to hand out. You have masqed out on your screen shots. They are private addresses and there is no reason to do that.
You set your subnet-specific IP address that will apply to vlan10 and wlan0.1 on br1, NOT ON vlan10 or wlan0.1. And the IP address cannot be quad zero. I think you should probably reset the router(s) and start over.
I agree, and that is exactly how I had it set up until @plawer suggested otherwise. I have no idea how his system could be working like that. All his bridges are quad zeros, which makes no sense at all.
I have since changed mine back to 10.1.0.5 on br1.
I think there is some misleading information being given out in this thread.
As it is now, R1 is working. It hands out addresses on both wl0.1 and on the other end of the three managed switches chain to my PC's secondary ethernet card.
What is not working is R2. The next three code entries are from R2 (Netgear R6250)
Code:
1: lo: <LOOPBACK,MULTICAST,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
valid_lft forever preferred_lft forever
2: teql0: <NOARP> mtu 1500 qdisc noop state DOWN qlen 100
link/void
3: ctf0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:23:6a:00:00:00 brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN qlen 1000
link/ether 9c:3d:cf:04:22:b0 brd ff:ff:ff:ff:ff:ff
5: vlan1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP qlen 1000
link/ether 9c:3d:cf:04:22:b0 brd ff:ff:ff:ff:ff:ff
6: vlan2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP qlen 1000
link/ether 9c:3d:cf:04:22:b0 brd ff:ff:ff:ff:ff:ff
7: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UNKNOWN qlen 1000
link/ether 9c:3d:cf:04:22:b2 brd ff:ff:ff:ff:ff:ff
8: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UNKNOWN qlen 1000
link/ether 9c:3d:cf:04:22:b3 brd ff:ff:ff:ff:ff:ff
9: vlan10@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br1 state UP qlen 1000
link/ether 9c:3d:cf:04:22:b0 brd ff:ff:ff:ff:ff:ff
12: wl0.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN qlen 1000
link/ether 9e:3d:cf:04:22:b3 brd ff:ff:ff:ff:ff:ff
inet 192.168.5.1/24 brd 192.168.5.255 scope global wl0.1
valid_lft forever preferred_lft forever
13: wl0.2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br1 state UNKNOWN qlen 1000
link/ether 9e:3d:cf:04:22:b4 brd ff:ff:ff:ff:ff:ff
14: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether 9c:3d:cf:04:22:b0 brd ff:ff:ff:ff:ff:ff
inet 192.168.254.13/24 brd 192.168.254.255 scope global br0
valid_lft forever preferred_lft forever
15: br1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether 9c:3d:cf:04:22:b0 brd ff:ff:ff:ff:ff:ff
inet 10.1.0.5/24 brd 10.1.0.255 scope global br1
valid_lft forever preferred_lft forever
If I add 0t (physical port 4) to VLAN 1 it creates a network loop. Here is the startup code:
Code:
#vlans
swconfig dev eth0 vlan 1 set ports "0t 1 2 3 5t"
swconfig dev eth0 vlan 2 set ports "4 5t"
swconfig dev eth0 vlan 10 set ports "0t 5t"
swconfig dev eth0 set enable_vlan 10
swconfig dev eth0 set apply
vconfig add eth0 10
ifconfig vlan10 up
brctl addif br1 vlan10
The startup code for R1 (EA8500) is very similar and as mentioned earlier, appears to be working correctly.
Code:
#vlans
swconfig dev eth0 vlan 1 set ports "0t 1 2 3 4t"
swconfig dev eth0 vlan 2 set ports "0t 5"
swconfig dev eth0 vlan 10 set ports "0t 4t"
swconfig dev eth0 set enable_vlan 10
swconfig dev eth0 set apply
vconfig add eth0 10
ifconfig vlan10 up
brctl addif br1 vlan10
_________________ 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.
