Have not tested it, will try to understand it first.
-7 AP need to be setup as simple as possible.
-I have a working MT main router with all configuration, CAPsMAN, vlan and trunk.
-CAP it booted in CAP_Mode and connected to the trunk on the main MT router.
But
I dont understand how the CAP get all other information, CAPsMAN only handle the wifi stuff, not setting up the bridge and other thing?
In CAP mode, the cAP has no VLAN settings at bridge level, it just looks for CAPsMAN on the bridge using L2 communication or, if it gets an IP address of the CAPsMAN via DHCP along with its own IP settings, it also tries to connect to that CAPsMAN. The rest of the behaviour depends on the local-forwarding setting - if CAPsMAN says local-forwarding=no, the wireless frames are delivered encapsulated to the CAPsMAN machine and converted to Ethernet ones there. If local-forwarding=yes, the frames are converted to Ethernet ones already at the CAP and injected to the local bridge. VLAN tagging is done in the wireless driver, so they appear on the bridge already tagged if this is what the datapath specifies.
The “CAPS Mode” configuration. That can be applied either by pressing reset for over 10 seconds or via /system/reset configuration (and choose CAPS Mode).
# jan/19/2022 17:19:57 by RouterOS 6.49.2
# model = RBmAPL-2nD
#
# ether1 is connected to MT router with trunk for vlan_10,20,30
# vlan_10 is trusted and the ip at ether1
# mAP is only a wifi AP nothing else, all is done in the MT.
/interface bridge add name=bridge1 vlan-filtering=yes
/interface wireless name=wlan-10...
/interface wireless name=wlan-20...
/interface wireless name=wlan-30...
/interface vlan add interface=bridge1 name=vlan10 vlan-id=10
/interface list add name=BASE_WAN
/interface bridge port add bridge=bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=ether1
/interface bridge port add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged ingress-filtering=yes interface=wlan-10 pvid=10
/interface bridge port add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged ingress-filtering=yes interface=wlan-20 pvid=20
/interface bridge port add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged ingress-filtering=yes interface=wlan-30 pvid=30
/interface bridge vlan add bridge=bridge1 tagged=ether1,bridge1,vlan10 untagged=wlan-10 vlan-ids=10
/interface bridge vlan add bridge=bridge1 tagged=ether1 untagged=wlan-20 vlan-ids=20
/interface bridge vlan add bridge=bridge1 tagged=ether1 untagged=wlan-30 vlan-ids=30
/interface list member add interface=vlan10 list=BASE_WAN
/ip address add address=192.168.10.6/24 interface=vlan10 network=192.168.10.0
/ip dns set servers=192.168.10.1
/ip route add distance=1 gateway=192.168.10.1
The config is for NO capsman!
Please take a look at this config, i have cut it to minimum.
mAP is connected to another MT router trunk for all processing.
ether1 (trunk) at mAP is connected to trunk at MT router.
All work DHCP,DNS,FW, and speed is ok about 30Mb down and 45Mb up.
In another test when using capsman speed is so low 3-4Mb both way.
Is my config ok (it all work but maybe i just lucky:-) )?
Why is speed lower in download than in upload, i see that on other MT ap too, Made minimum config and no vlan, only basic config to test speed.
Why is capsman so slow. (I need to do all in the MT main router!)
AP can also be its own CAPsMAN.
I set up CAP AC as AP with itself as CAPsMAN, and then a little cAP Lite in a blackspot somewhere as an extra CAP AP to the CAPsMAN controller (CAP AC).