RouterOS 7.19 has a new option:
wifi → datapath.traffic-processing=(on-cap OR on-capsman)
How to use this?
Does anyone have a positive experience?
There is still no documentation.
good catch. I’m going to sub to hear if anyone has information. This their potential fix to performance issues when using Capsman?
Is that for handling traffic on CAPsMAN as it was on CAPsMAN V1?
Doesn’t work…
I would say so
How do you expect it to work and how did you test?
Expected traffic processing on capsman, i.e. no need to create bridges on CAPs.
The “datapath not supported” message appeared on CAP’s wifi interface after enabling this setting. So i assumed it doesn’t work. Maybe some additional configuration needed…
What’s really needed is the documentation.
You aways need to assure there is a communication path from caps to manager so a bridge is needed on caps.
Default config does take care of that.
The only thing this setting should change is that traffic from caps-clients is not forwarded locally from caps device itself but first send to capsman manager (encapsulated) and from there it is decapsulated and then forwarded to the final destination.
Haven’t tested it myself yet but that’s how it works for legacy capsman.
Not true.
WAP01 > /interface bridge print
Flags: X - disabled, R - running
Works absolutely fine without any bridge. What is really needed is documentation route to capsman (which is indeed exist)
WAP01 > ip route print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADS 0.0.0.0/0 192.168.100.1 1
1 ADC 192.168.100.0/24 192.168.100.251 ether1 0
P.S. This is obviously ROSv6.
This CAP is hap ac2. I suspect option is not intended to work on wifi-qcom-ac drivers…
Afaik ac ww2 will no receive any new features, including this new datapath mode.
Before anyone comes up with more theories about support: has anyone actually tested whether “traffic-processing: on-capsman” works in a wifi-qcom setup?
I’d also like to know this answer if backwards** compatible with wifi-qcom access-points. Or requires the qcom-ac driver…
Tested this on Cap AX. Pushed a new config with a new Datapath linked to the CapsMAN unit.
Did not work. Got the same issue on CapsMAN unit. “datapath not supported”. On the CAP I saw nothing at all.
Both CapsMAN CAP are on 7.19.1 so I suspect this is something new that I hope gets introduced sooner or later but we just see nuggets of this right now.
Or MT is just messing with us 
I’ve tested that on 2x wAP ax with ROS 7.19.1 with the following setup:
- each AP has one big trunking bridge
- each AP has VLAN Tagging for multiple WiFis
where I expected, that traffic-processing=cap means, that the traffic is leaving the AP to the network directly instead of forwarded to capsman and then send to the network.
Result: not working.
The next big disadvantage with traffic processing on CAP is you can not isolate the clients! (Bridge Horison) Guest WIFI
And a huge Configuration on the Switches with multiple VLAN and many CAPs.
I hope the feature Traffic Processing on-capsman ist working soon.
On the Old Capsman there works fine.
1 Like
There were always performance issues with capsman-forwarding with legacy capsman. It’s yet to be seen how new capsman will fare in this regard.
We apologize for the confusion. This parameter is meant to be used with “non-wifi-qcom” (non-Qualcomm) devices 
As of this moment, it will not allow “wifi-qcom” capsman-forwarding. “wifi-qcom”, at this time, supports only “local-forwarding”…but! Rest assured, we are aware that people are requesting this addition for wifi-qcom drivers as well, and we will see what we can do in the future versions.
5 Likes
@denissMT Thanks or that clarification…
…This a blanket statement for the Qualcom wireless drivers?.. All MikroTik “consumer” wireless is Qualcom. Or this mean for “AX” devices, not wifi-qcom-ac.
Fix your sh*T… This is why we’ve been leaving MikroTik. CAPsMan in THEORY, in perfect environment is nice. But too complex, and the default AP profiles are not good enough out of the box.
RouterOS6 CAPsMAN was better [AC]