Hi, I’ve tried to figure it out myself but I haven’t succeed, I need your king help.
I’ve an existing network consist of HEX as gateway and capsman, one AC3 and 3 AC Lite, all at 7.19.1,I’ve decised to add an AC2 but I’ve decided to spend more and buy an AX2 to test WiFi6, I can’t make it join Capsman.
This router has qcom and wireless package isn’t working on it, anyway I would take advance of qcom. For MMIPS there isn’t qcom, as well for MIPSBE, I’ve read that HEX has both Capsman native, where is this “wave2”? I can’t find it, for me everything is similar as always.
How can I mae the ax2 qcom join the existing Capsman? Where is the wave2? How can I make other APs join the wave2?
Than you for support
I’ve read that
Unfortunately I don’t think that there is qcom package for MMIPS (hex) so there isn’t native support for it. What you can do is to use one of your other devices a a gateway, and great candidate for that would be ax2
Yes, AX2 can act as an CAPsMAN controller for both versions. WiFi tab is for new CAPsMAN and Wireless is for legacy wireless and CAPsMAN (I don’t remember if old capsman is under wireless or dedicated capsman tab)
You can perfectly use Hex as controller for wave2 devices as long as it runs a ROS7 version >=7.13
Basic hooks are present in ROS then for it to act as capsman controller for wave2 devices.
It’s all in the Wifi menu tree.
I’ve done it already. I even did it as Proof Of Concept with mAP.
If you also want to retain legacy capsman function, you can try to add wireless package again.
BUT … be careful with that 16Mb storage…
Publish a text export of your configurations. Remove serial number and password data from it.
I have the hEX doing great as a CAPsMAN controller. And there is plenty of free space.
Thank you a lot mates for helping here
So your suggestion is to turn off the legacy capsman present in wireless, and activate the capsman under wifi, but how ativate it? Where is the “manager” button?
Actually I’ve copied/adapted all configs of legacy capsman into wifi, but I can’t find there how to activate capsman, I can only activate caps, which on HEX has no reasons.
The AX still looking for capsman, sending to HEX request (I can torch them) but no answers from capsman.
WHen thsi will be solved, what should I be adviced to do on wifi2 interface to have good results? To make caps do the roaming in a good way? There are new parameters, there is not more the 2.4GHz B, should I choose N? G means that N is also included?
Thanks
I’ve found the button under the Remote CAP tab, wow they put it there, I can see the AX connected now but no its radios, why? THe provisioning is correct, I can’t understand how it works. Why it’s so different from legacy?
I do have 3 AC lite, they are not qcom and can’t load that, I have AC3.. maybe it’s possibile on this one?
So yes I need a mixed mode, how to do that? Should I use only wave2 or I have to specify on wave2 only AX and on legacy the others? Will the 2 capsman dialogue each other after? What a messy here..
;y question about N or G is on wave2, considering the legacy caps
I don’t thin it’s necessary to put a diagram, consider you have one HEX, 3 AC lite, one AC3, one AX2 on the same LAN, having the same bridge.
I want to have capsman between then, simple.
If it’s not possible I’ll go crazy and I argue with Mikrotik, since I believe on this company and bought a new model, which is not compatible with the existing ones. Money wasted on WC!
I’m eventually open to use AX2 as capsman for all caps, but they should be roaming between each other!!
Thank you
PS: I stil not able to connect AX2 to HEX using wave2, I can see the AX2 but no radios! No logs, no errors, no help. I start hating this new wave2, why so complicated
PS2: can I downgrade AX2 to a simple legacy capsman and forget about WiFi 6? This is better than waste money on WC
Your choice if you want us to help you or not.
If you do not show your config, fine with me but then you are on your own.
Fact remains:
You can not have capsman functionality between legacy and wave2 devices.
You can not downgrade AX device to legacy wifi. It gets even better: you can use AX2 as legacy capsman controller but then you need to load wireless driver and then you will loose your AX2-radio. You don’t want that either, do you ?
Simple as that.
More info: see here:
Accept it or not but that will not change.
PS only ONE AX2 ? Then why use capsman for it ? That’s making it really complicated.
Because I do need roaming between caps, I can’t create a second WiFi SSID with the same name, the devices will keep connected to the previous one until they will lose the connection, you know about all these problems already.
Thanks for clarify, I’m extremely disappointed I wasted my money buying a new AX2, since I believed a serious company give compatibility between its own devices, or at least advice markably to don’t mix technologies, and disancurage that.
Now I have to spend double money to buy an AC2, that’s simply horrible. F* Mikrotik!
Sorry but I can’t resist to tell that.
What do you suppose to see interesting on the config, if it is not possible to have roaming between capsman all become useless
Don’t go blaming someone else for your own mistakes … wrong approach.
You can not expect wifi4 and wifi6 devices to be fully compatible.
Not a single vendor will give you that.
Mikrotik Wifi4 drivers were developed completely in-house by Mikrotik.
Wifi6 drivers are taken over from their chipset vendor.
And then there is a quite substantial difference in capabilities between wifi4 and wifi6.
Hence the difference.
AX2 is a very good device (I have one at home and installed several with clients) but you have to use it standalone in your current environment.
Even with capsman, it will always be your client device which decides when it roams or not.
But only wave2 capsman will give you seamless roaming, sending out signals to clients it may be better to switch to another AP.
Not legacy capsman with wifi4. It doesn’t have those features.
The problem here which you do not want to see is that you have not been doing your homework.
Consider it learning money.
You saw something, you bought it, you noticed it did not work and then you came asking.
Yes, now I won’t believe more on MIkrotik, trust is lost, I will ask.
When you are staying on the same brand you expect compatibility, if not, a serous company warning about “not compatible”! Searching I haven’t found nothing about that.
I got the lesson, my bad.
Thank you for helping clear me, I wish it will not happen to someone else, hopefully this thread will help
Recap: why not use HEX as capsman? It can do wifi capsman with ROS 7.13+ and together with wireless package act as wireless capsman. Right or am I missing something?
No problem for me to run capsman on AX2, but I need radio from AX2 too and it should roaming with other caps. As the legacy capsman does, I don’t need more, I can forget about WiFi6
I can, then do the both capsman make roming fo devices between all caps? I dubt about that..
I need full roaming between caps, as it was without problems with legacy capsman
