Seems that you did just fine. What I did (near similar config) is this:
The difference? Using a specific (management) VLAN for communication with CAPsMAN and allow only tagged frames on the bridge and ether1 (I'm not using ethter2).
As you mention running wAP ac's as well, are you sure that the correct configuration is provisioned to the AX's?
Code:
interface bridgeadd admin-mac=XX:XX:XX:XX:XX auto-mac=no frame-types=admit-only-vlan-tagged name=bridgeLocal protocol-mode=none \ vlan-filtering=yes/interface vlanadd interface=bridgeLocal name=MGT-VLAN vlan-id=99/interface wifi datapathadd bridge=bridgeLocal comment=defconf disabled=no name=capdp/interface wifi# managed by CAPsMAN XX:XX:XX:XX:XX%MGT-VLAN, traffic processing on CAP# mode: AP, SSID: ssid, channel: 2462/axset [ find default-name=wifi1 ] configuration.manager=capsman .mode=ap datapath=capdp disabled=no# managed by CAPsMAN XX:XX:XX:XX:XX%MGT-VLAN, traffic processing on CAP# mode: AP, SSID: ssid, channel: 5700/ax/Ce/Dset [ find default-name=wifi2 ] configuration.manager=capsman .mode=ap datapath=capdp disabled=no/interface bridge portadd bridge=bridgeLocal comment=defconf frame-types=admit-only-vlan-tagged interface=ether1/interface bridge vlanadd bridge=bridgeLocal tagged=bridgeLocal,ether1 vlan-ids=50add bridge=bridgeLocal tagged=bridgeLocal,ether1 vlan-ids=51add bridge=bridgeLocal tagged=bridgeLocal,ether1 vlan-ids=99add bridge=bridgeLocal tagged=bridgeLocal,ether1 vlan-ids=53/interface wifi capset discovery-interfaces=MGT-VLAN enabled=yes slaves-datapath=capdpAs you mention running wAP ac's as well, are you sure that the correct configuration is provisioned to the AX's?
Statistics: Posted by erlinden — Sat Mar 29, 2025 9:48 am