Hi
simple configuration with one cAP and one CAPsMAN that is on two different MikroTik devices but datapath in CAPsMAN doesn’t work.
Datapath.bridge on the CAPsMAN for the configuration that manages the wireless interfaces on the remote CAP is set to bridge2 but the users connected via the CAP get the address from bridge1 which physically connects this two devices.
Is this is misconfiguration or datapath on CAPsMAN doesn’t work?
R-3-cAP.rsc (1.25 KB)
R-2-CAPsMAN.rsc (1.83 KB)
Any reason you want to work with multiple bridges (for wireless versus wired)?
As there is nothing mapped on bridge2, my assumption would be that being the reason.
If you want to make distinction, you might want to consider using VLAN’s. For the time being, you can test with setting the brdige to bridge1 on the datapath of the CAPsMAN.
Okay, I think the reason could be relevant if we were discussing a proposal for a different design.
I agree with my colleague that in the old CAPsMAN, the datapath configured to a specific bridge would direct traffic to the DHCP server attached to that bridge:
wifi1 → datapath1 → bridge1 → dhcp1 → ip pool1
wifi2 → datapath2 → bridge2 → dhcp2 → ip pool2
Now, local management doesn’t work this way—all WiFi networks receive IPs only from one DHCP1.
I’d like to note that in my setup, AX access points are in CAP mode and there are no errors.
Is this a bug or a configuration issue? Could it be that the datapath → bridge simply no longer works?"
with wifi ax and vlan filtering the datapath works perfectly. its cap is also essential to generate the slave interfaces dynamically in bridge Port and bridge vlan
It might not work because the master wifi interfaces need to be added to the bridge manually
Settings from CAPsMAN (datapath as well) are applied on CAP device.
In your setup, you’re setting
/interface wifi configuration
add country=Serbia > datapath.bridge=bridge2 > disabled=no mode=ap name=cfg1 security.ft=yes .ft-mobility-domain=0x1 .ft-over-ds=yes ssid=“EF WiFi”
but CAP device only has bridge0 and bridge1. CAPsMAN only provisions radio interfaces (and creates slave devices when required), but doesn’t touch the rest of config (apart from minor changes to bridge VLAN settings if VLANs are configured on radio interfaces).
A general remark: in modern times there’s no need for multiple bridges in 99.99% of cases. VLANs do the work just fine.