CAPsMam + VLAN on wifi-qcom-ac enviroment where CAPsMam it self has Wifi

RouterOS Wireless Networking
1

Hi!
With help from https://help.mikrotik.com/docs/spaces/ROS/pages/224559120/WiFi#WiFi-CAPsMAN-CAPVLANconfigurationexample:
I did manage perfectly fine wifi-qcom-ac environment where CAPsMAN is RB4011iGS+ which has no Wifi it self.
In home environment I have Chateau 5G as main router and tried to move all CAP’s and Chateau itself on wifi-qcom-ac and . I successfully can get correct VLAN’s on CAP’s, but I cannot get VLAN on Chateau 5G itself. Is this even possible? Where is the catch?

/interface bridge
add auto-mac=no name=bridge port-cost-mode=short vlan-filtering=yes
/interface vlan
add interface=bridge name=vlan_Viesi vlan-id=20

/interface bridge port
add bridge=bridge interface=ether1 internal-path-cost=10 path-cost=10
add bridge=bridge interface=ether2 internal-path-cost=10 path-cost=10
add bridge=bridge interface=ether3 internal-path-cost=10 path-cost=10
add bridge=bridge interface=ether4 internal-path-cost=10 path-cost=10
add bridge=bridge interface=ether5 internal-path-cost=10 path-cost=10

and here i have 1st problem. I did created under wifi1 wifi21, but it disappeared and bridge interface went as *4A.
/interface wifi
add disabled=no master-interface=wifi1 name=wifi21
add disabled=no master-interface=wifi2 name=wifi22

add bridge=bridge interface=*4A pvid=20
add bridge=bridge interface=*4B pvid=20

/interface bridge vlan
add bridge=bridge tagged=bridge,ether1,ether2,ether3,ether4,ether5 vlan-ids=20

and untagged dispier.

/interface wifi datapath
add bridge=bridge name=DP_AC
/interface wifi security
add authentication-types=wpa2-.......*

/interface wifi configuration
add country=***** datapath=DP_AC disabled=no mode=ap name=MAIN-2Ghz security=S*****a ssid=*****
add channel.skip-dfs-channels=all country=***** datapath=DP_AC disabled=no mode=ap name=MAIN-5Ghz security=***** ssid=*****
add country=***** datapath=DP_AC disabled=no name=Guest-2Ghz security=***** ssid=*****
add channel.skip-dfs-channels=all country=***** datapath=DP_AC disabled=no name=Guest-5Ghz security=***** ssid=*****

tried with and without this
/interface wifi cap
set discovery-interfaces=bridge enabled=yes slaves-static=yes

/interface wifi capsman
set enabled=yes  require-peer-certificate=no upgrade-policy=none
/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=MAIN-2Ghz name-format=2Ghz-%I slave-configurations=Guest-2Ghz supported-bands=2ghz-n
add action=create-dynamic-enabled disabled=no master-configuration==MAIN-5Ghz name-format=5Ghz-%I slave-configurations=Guest-5Ghz
Wireless, CAPSMAN, update from pre 7.13
2

The intention is that local wifi interfaces are not provisiobed by CAPsMAN (running on same device). With new wifi, CAPsMAN and local wifi setup share same configuration profiles, one can apply same profile (e.g. security) both to CAPsMAN and local interfaces. Local radios will still work with other CAP devices with regard to mobility features (because it’s the same wifi core process communicating both with local and remote radios).

3

hi!
With help form MT support as it turs out it can be achieved only after 7.17rc1.
You should do as per instructions in help but with this twist on CAPsMAN

/interface list
add name=wifiliste_guest
/interface bridge port
add bridge=bridge interface=wifiliste_guest pvid=20
/interface wifi datapath
add bridge=none disabled=no interface-list=wifiliste_guest name=Local_VLAN

Where add bridge=none is only CLI.
And then this datapath is configured and provision only to local CAPsMAN wifi only
Many thanks to MT support!