My question as in the topic, in other words does it work as a CAP in 802.11ax standard?
Has anyone already tested the hAP ax²?
Hi,
I think so, if you unpack the wave2 drivers you will see there driver for CPU which is HPA AX2 using. I doubt that MT develop their drivers in the past they did it and thats the reasen why we do not have working routing till now… MT said that they are working on capsman working with wave2 but it could take years 
So far you have to choose between wave2 performance and CAPsMAN provisioning. It’s not possible to have both.
And my guess (I don’t have hAP ax2, my only experience is from Audience) about answer to the question in the subject of this thread: hAP ax2 probably doesn’t require wave2 drivers. Which means you can get it work as CAP (under CAPsMAN provisioning), but it’s wireless performance will be … well, mediocre at best.
Didn’t the initial announcement video state it WOULD NOT WORK WITH CAPS-MAN at release.
No idea (as I said, I don’t gave any of ax2 devices). I would assume that legacy wireless driver works on these devices and if it does, it probably works with CAPsMAN. Certainly this would thrash performance to the point where one should be questioning investment into this device (instead of some N-device).
hAP AX can only work with the wifiwave2 package. We do not have the “old” self made driver for this new chip anymore.
CAPsMAN for wifiwave2 package is in development.
That would make the proper reply to this thread title…
Yes.
Thank you @normis for your clear answer.
It is very good news that wave2 CAPsMAN development is in progress.
Would you share with us the schedule, when is it expected to be released in the ROS beta?
It’s a good, but old news.
The “news” is already inside the hAP ax² presentation video…
MikroTik do not share any schedule.
I bought ax2, I’m really looking forward to when the capsman will be delayed
Capsman is already released for the AX products. You are replying in an old thread.
Old version. Install 7.7
Normis, as often, jumping the gun again … I would hardly call beta version as “release”. And I’m not arguing here quality of release versions here (some were awful, some are great, most are somewhere in between).
So it would be correct if Normis wrote “capsman will be released in next ROS version, v7.7. It is possible to try it out as beta version 7.7beta9” or something in this line.
Released means available for anyone to install.
If you want latest and greatest features first, you must be willing to install beta.
Well yes. This is the statement that explains Mikrotik view which is pretty unique in ICT world and most of us don’t agree with it (beta available to everybody is a “public beta” not a release). But then, some of us love Mikrotik so much that are willing to do things we wouldn’t with other vendors. Such as installing beta versions 
In version 7.7 beta 9, which I installed, capsman is available via the terminal, but is still missing from the interface.
http://forum.mikrotik.com/t/v7-7beta-testing-is-released/161807/86
The crucial part to understand “why not in menu?”
*) wifiwave2 - added initial CAPsMAN support (only compatible with wifiwave2 interfaces) (CLI only);
I admit, I was not attentive.
Hello everyone, I have a doubt about the capsman compatibility on mixed wifi wave2 and non wave2 devices.
According to this guide
https://help.mikrotik.com/docs/display/ROS/WifiWave2#WifiWave2-De-authentication
“WifiWave2 CAPsMAN can only control WifiWave2 interfaces, and WifiWave2 CAPs can join only WifiWave2 CAPsMAN, similarly, regular CAPsMAN only supports non-WifiWave2 caps”
My question here, is there a roadmap for supporting mixed wifiwave and non wave2 devices on the same capsman or will this remain separated?
I ask this because we manage a +40 non wave2 devices environment with capsman and if important for us to know if we have to continue growing with old devices with non wifiwave2 support or at somepoint we will be able to keep using our legacy APs and add new ones with wifiwave2 support on the same capsman?