When is CAPSMAN going to manage the WMM parameter?? Something sorely lacking in CAPSMAN.

Capsman is for lazy masochists who cant see the forest from the trees. They think capsman is going to be so efficient but then beat their heads against the wall for months trying to get it to work, only to find that the wifi performance at the end, the really important functionality is just not there. That is my short story for today.

Per Ardua Ad Wifi6

Quite biased comment, no ?

Capsman has it uses.
Maybe not for you but others surely can use it positively.

If you use capsman, then some settings are enabled by default and some cannot be changed. As for WMM it is enabled when using capsman. I am unsure why you would not want to use it.

Remember that just enabling WMM might do nothing for the traffic.
It is up to the user to configure the packet priority (based on VLAN, 3 high bits DSCP, ....) with mangle rules, and to enable A-MPDU where needed.

RouterOS does not set priority by default (eg copied from DSCP). So everything is priority "zero", and the priority zero is transmitted in WMM as "best effort".
In IT we know that "best effort" is rather low priority. The WMM parameters for WMM priority zero are not the best. (They are the same as for non-WMM 802.11n/ac)
I don't know where the "Aifsn,CWmin,CWmax,TXOP" standard defined WMM parameters can be seen or set. Except they are clearly communicated in the beacon sent out as AP.
viewtopic.php?p=901234#p864106
Using anything else than priority zero, will also disable the A-MPDU packet aggregation in the default standalone configuration.

I wonder if CAPsMAN does any of these extra steps.

I promise to try capsman when MT sells capaC6

I promise to try capsman when MT sells capaC6

Deal !