Not sure which example you used for your config but you are making things mighty complicated putting everything together learning capsman and then putting VLAN into the mix as well.
You combine now a full VLAN aware switch with a caps device in pure caps mode, that will not work as expected.
And I was missing that router somewhere… until I saw this thread again on my computer.
When I look at your config (latest version ?)
- you specify 2 VLANs but there is only 1 set of router services for that VLAN (no DHCP on MGMT vlan). Is that intentional ? Other router taking care of the missing parts ? Do you specify the IP addresss for MGMT vlan manually on your caps device ? Since it’s in CAPS mode, I guess not …
- where does pvid=5 come from on some of the ports on bridge ? It’s nowhere defined on your CRS ? Is there another router handling that part ?
- your vlan6 is nowhere defined in interface list. Trusted ? LAN? … whatever. Not that it matters, there is no firewall on that device. Even better to remove those interface lists completely since they make no sense on that CRS as it is configured now.
- capsman is enabled but you connect it to bridge. Might be better to use vlan4 there.
In short: your mixing quite some things making it quite confusing and since it doesn’t work …
First decide where you want to have the router services handled. Personally (and it’s more logical), since you have a separate router, let that one take care of things.
Unless you can not change that router config ?
Decide what will be your MGMT layer to control CAPS devices (I assume VLAN 4).
On that caps device, you will also have to add a VLAN to bridge with pvid=4, add dhcp client to that interface and caps discovery interface as well.
No need to enable VLAN filtering on that caps (it works in hybrid mode). Any wifi interfaces added later on will be added dynamically with the correct vlan id.
Test and report back please.