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.
-
-
toxicfusion
Member
- Posts: 351
- Joined:
Re: New option on RouterOS 7.19 datapath.traffic-processing
good catch. I'm going to sub to hear if anyone has information. This their potential fix to performance issues when using Capsman?
-
-
alexwaller
just joined
- Posts: 19
- Joined:
Re: New option on RouterOS 7.19 datapath.traffic-processing
Is that for handling traffic on CAPsMAN as it was on CAPsMAN V1?
Re: New option on RouterOS 7.19 datapath.traffic-processing
Doesn't work....
Re: New option on RouterOS 7.19 datapath.traffic-processing
I would say soIs that for handling traffic on CAPsMAN as it was on CAPsMAN V1?
Re: New option on RouterOS 7.19 datapath.traffic-processing
How do you expect it to work and how did you test?Doesn't work....
Re: New option on RouterOS 7.19 datapath.traffic-processing
Expected traffic processing on capsman, i.e. no need to create bridges on CAPs.How do you expect it to work and how did you test?
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.
Re: New option on RouterOS 7.19 datapath.traffic-processing
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.
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.
Re: New option on RouterOS 7.19 datapath.traffic-processing
Not true.a bridge is needed on caps.
Code: Select all
WAP01 > /interface bridge print
Flags: X - disabled, R - running
Code: Select all
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
Re: New option on RouterOS 7.19 datapath.traffic-processing
This CAP is hap ac2. I suspect option is not intended to work on wifi-qcom-ac drivers...The "datapath not supported" message appeared on CAP's wifi interface
Re: New option on RouterOS 7.19 datapath.traffic-processing
Afaik ac ww2 will no receive any new features, including this new datapath mode.This CAP is hap ac2. I suspect option is not intended to work on wifi-qcom-ac drivers...The "datapath not supported" message appeared on CAP's wifi interface
Re: New option on RouterOS 7.19 datapath.traffic-processing
Before anyone comes up with more theories about support: has anyone actually tested whether "traffic-processing: on-capsman" works in a wifi-qcom setup?
-
-
toxicfusion
Member
- Posts: 351
- Joined:
Re: New option on RouterOS 7.19 datapath.traffic-processing
I'd also like to know this answer if backwards** compatible with wifi-qcom access-points. Or requires the qcom-ac driver....
Re: New option on RouterOS 7.19 datapath.traffic-processing
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
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
Re: New option on RouterOS 7.19 datapath.traffic-processing
I've tested that on 2x wAP ax with ROS 7.19.1 with the following setup:
Result: not working.
- each AP has one big trunking bridge
- each AP has VLAN Tagging for multiple WiFis
Result: not working.