I tried to configure main router and WiFi access points using VLANs as I have 3 different networks.
This appeared to work fine with OpenWRT v23.05.5 with main router GL-MT6000 and AP TP-Link AX23. Once I tried to connect Cudy WR3000S with v24.10.1 (minimum available for the model) as 2nd AP, I met problems:
Applying changes starts to hang device once I added ports to VLAN bridge (more specific - all ports were Ok, exept eth0). After Save&Apply click it was necessary to disconnect power and reload device.
Wiless networks can't be saved if assotiated with VLAN indexed networks (like vlan.10).
All mentined above work good on v23.
I tried to upgrade TP-Link AX23 to v24 (clean system set up) - VLAN didn't to work there as well.
Same things happened to me...
LuCI wireless editor Save button only works if one chooses a bridge based interface as the attached network. If interface is based on a VLAN dot device, the Save button doesn't work.
No, it is not a problem to configure VLANs themselves on v24 and to assign interfaces.
For example, I created interfaces lab, nic, sun and linked them to VLAN.10, 20 and 30
This works on v23 and v24
But WiFi networks can't be saved if I select interface linked to VLAN (sun linked to vlan.30):
This is often an issue of sequencing. My preferred method is to edit the config files directly so everything gets applied at the same time. But it is possible to do with LuCI if you're careful.
There was one other similar report of this (linked by @pluffmud), but I don't think this is a universal issue, so not exactly sure what to make of it.
But let's start by reviewing the complete config on both devices.
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
Hi, this is configuration of my Cudy WR300S access point.
As I mentioned, I was able to configure WiFi only for non-VLAN interfaces.
For VLAN interfaces "Save" button doesn't work.
You need a bridge device in the interface in order for the wireless to work.
It's the way Linux wireless networking works, it's not really a Openwrt bug/thing, it's the way it's designed to work.
So you need to make a bridge on top of the bottom bridge to mimic how things used to work. So as an example...
make a bridge device called "sunbr"
then add 'VLANS.30' as a bridge port for sunbr
then for the 'sun' interface set the device to 'sunbr'
Off topic:
I'm not sure if there is a way to configure things where only one bridge is still getting used. There's a sneaky way i've found.
Big Bridge with wireless interfaces added to the filtering: