(WARNING: TO AVOID TRIGGERING SOME, KNOW THAT I'M RUNNING WAY MORE THAN 3 CAPS)

In all seriousness is anyone else having this issue...I'm not seeing any type of interface stats (TX,RX ,etc) on the CAPSMAN (wifi) controller when I monitor-traffic for any CAPax devices. The CAPS are passing traffic and the SSIDs are working as intended and using the correct VLANS. I can see traffic as expected on individual interfaces when ssh'd into the CAPax device but zero stats on the controller. My CAPSMAN (wireless) controller (same device) running CAPacs are displaying stats as expected.

Ack, can confirm. Already reported by several people on the forum as well

Thank you, and my apology I did a search but didn't see anything.

Only 3 caps ?
( I have a setup at home for testing with 2)


In all seriousness, might be a result from no capsman forwarding anymore, only local forwarding.

Only 3 caps ?
( I have a setup at home for testing with 2)


In all seriousness, might be a result from no capsman forwarding anymore, only local forwarding.

I try to keep up on the forums (the best anyone can) and why that issue always seems to be a hot topic, I don't know but I had to throw it in but only out of a little humor.

In case you missed it, my response was with an equally funny undertone

Only 3 caps ?
( I have a setup at home for testing with 2)


In all seriousness, might be a result from no capsman forwarding anymore, only local forwarding.

there is no local forwarding option in wifi capsman anymore. must admit I am new to capsman too but I'd expect it to show stats.

And how would it know if traffic is not passing there ?

If you still can, test with old capsman and local forwarding. What does it show or not ?

To be honest: I don't ask myself how it can know.

How can the capsmanager know the interface of a cap at all? how can and how why?

When stats are not implemented on purpose (because of either technical limitations, wrong config, etc). then it is MTs duty to clarify:

- in the docs
- on the winbox/CLI/webfig screen

It is not the user in duty to reverse engineer how capsman may work and maybe it may not be implemented.

In that case you should ask support.
They should know.

And please be so kind to let us know their response as well (because now I am curious too )

And how would it know if traffic is not passing there ?

It might if CAPs collect the stats and report it to manager. As we all know, manager, who doesn't know what subordinates are doing, can't do his job efficiently. Right?

That's a possible option.
But only support will be able to tell for sure.

FWIW just tested in my lab setup (I got a Hex setup with both capsman environments and then AX2 and mAP as APs):

Old capsman with local forwarding -> zero counters on interfaces visible on capsman controller. They do show on local AP device.
Local forwarding disabled and bridge defined in datapath (a.k.a. capsman forwarding) -> counters start to flow on capsman controller. Nothing visible anymore on local device.

It's also noticable when you see the interface line itself on the local AP device.
local forwarding -> interface line is black
capsman forwarding -> interface line is greyed out. Nothing to see there.

So my conclusion is that wave2 behavior is exactly the same as it was in the past for that local forwarding part.
With a not so insignificant minor detail that capsman forwarding does not exist anymore (yet ?) in wave2-environment. Only local forwarding remains.

Only way I can think of to sort-of "recreate" this local forwarding is to make use of EOIP and force all data to run over there.
AP only able to see capsman controller, nothing else.
Setup EOIP between AP and controller (which is possible since controller can be reached, nothing else)
Attach EOIP to bridge, default route for AP going over that EOIP link.
Result: All AP traffic visible on capsman controller.

Could work, I believe ... another test project

MT support reply:

Hello,

Thank you for contacting MikroTik Support.

wifi CAPsMAN works in the same manner as "local-forwarding" did on wireless CAPsMAN. The CAPs don't send traffic usage information to CAPsMAN.

Best regards,

MT support reply:

Hello,

Thank you for contacting MikroTik Support.

wifi CAPsMAN works in the same manner as "local-forwarding" did on wireless CAPsMAN. The CAPs don't send traffic usage information to CAPsMAN.

Best regards,

CAPsMAN features in AX are reduced to configuration only. Really disappointed of the 'local forwarding only' option.

Is this permanent or temporary?

That's another question to support.