I am setting up multiple bridged VLANs on a GL-MT6000 (OpenWrt 24.x snapshot) for use with a managed switch.
Each VLAN has:
a br-lan.X subinterface created through Bridge VLAN Filtering (DSA)
its own firewall zone
its own DHCP scope
a Wi-Fi SSID assigned directly to that interface (lan10, lan20, lan30, lan40, lan50, lan60, lan70, lan99)
The VLAN interfaces appear correctly in LuCI, and the SSIDs can be assigned to them.
However, a reproducible problem occurs:
After every reboot, none of the SSIDs attached to VLAN interfaces receive DHCP.
Windows reports "No DHCP" and self-assigns a 169.254.x.x address.
The only way to make an SSID work is to do the following trick:
Edit the VLAN interface (e.g., lan20)
Temporarily assign it to the lan firewall zone
Save & Apply
Reassign it back to its correct firewall zone (e.g., vpnonly, momnet, quarantine, mgmt99)
Save & Apply again
After this, DHCP works instantly and Wi-Fi clients get an address until the next router reboot.
On reboot, the VLAN/SSID again fails to hand out DHCP, and the entire process must be repeated.
Basically it seems like the problem is the wifi ssid doesn't stay attached to the vlan's I make. I run that little switch the firewall zone to lan then back to what it should be and everything then works but it's not a permanent fix. I'm trying to work towards setting up a vlan that uses wireguard but creating the tunnel has been impossible...I'm wondering if this issue has anything to do with it. But for now, I need to make sure the vlan's work properly at all times before I focus on getting wireguard to work. Also, look at the screenshot I'm sharing...It shows ONE vlan seems to have it's wifi ssid attached while the rest do not even though they all have a wifi ssid created for them all with the vlan selected as the device the ssid should be associated with. Also notice, Br-lan1, br-lan, br-lan.99 are all green...Those are the only ones that work through reboots. 1 and and br-lan are connected to the lan firewall zone but 99 is connected to it's own firewall zone but also seems to have it's wifi ssid permanently attached. I don't know what I did wrong here.