I have network with router done by hEX with running CAPsMAN and severals AP - one is RBcAPGi-5acD2nD, one is hAP ac^2 and now I want and now I want add next one AP - hAP ax^2. Problem is that there isn’t connection to CAPsMAN when I enable CAP.
Is there any chance to get working ? Or I must change any other component (hEX ? ) in my network to get working CAP on all AP ?
Thank you for your help
You cannot combine APs using “wireless” driver and APs using “wifi-qcom(-ac)” driver into a single CAPsMAN.
shall I use “wifi-qcom(-ac)” for all ? Or what is a solution ?
Indeed, only use wifi-qcom(-ac) driver.
Yes indeed, except that the RBcAPGi-5acD2nD will not be able to use that driver, so it would have to be replaced by something newer. And on the hAP ac^2 that driver could in theory be used but the space on the flash will become very very tight and there may be issues when upgrading.
So in practice it will probably be better to keep using wireless with CAPSMAN for those, and configure the new device separately.
I’m not sure if I understand it correctly. Means run “old” capsman and “new” capsman simultaneously on the hEX router ?
That cannot be done.
No, I mean to configure the ax^2 manually so it will work in your network. Apply similar settings to what you now have in CAPsMAN in the local configuration of the ax^2.
Or: you could configure CAPsMAN on the ax^2 and use that to manage it itself, and use that as a starting point for when you are buying more new-generation MikroTik devices.
so I did a upgrade of AC2 to “new” CAPsMAN :
and it’s working all together
but I must check configuration under my hEX, because configurationCAPsMAN wasn’t assigned automaticaly.
Actually the cap ac CAN use wifi-qcom-ac
A big problem in this context is that MikroTik make completely different devices and then release them under the same model name. So it is difficult to know what he really has.
There are MIPSBE and ARM32 versions of the cAP AC, and “hEX” is even more nondescript, with that name there exist many different devices. However most of them aren’t ARM and because he had older stuff as well I assumed his hEX wasn’t an ARM model either.
I’m sure you will regret that. But I warned you, so I do not care about that.
I think you mean the wap AC which has both arm and mipsbe versions.
Afaik the cap only was released as arm.
Understand, but no other easy working solution. I will use a Ac2 in my garage as AP till I will upgrade to new HW.
Agree @itimo01, the cAP ac was only ARM in contrary to the wAP ac.
Have been running cAP ac, cAP ac XL and wAP ac with the wifi-qcom-ac driver with no problems at all (VLAN is a pain in the butt to configure, butt just works fine).
Just as info:
Oh yes you can.
I already did so on a stupid mAP and Hex.
Just need to load wireless package since base hooks are present as of ROS 7.12 for wave2 part capsman. Wireless package is needed then for legacy wireless support (so don't do this on AX device, you will loose radio when using that as combined controller).
You will end up having 2 different capsman controllers running on the same device.
Each controller will act on their respective APs but it works.
No seamless roaming between both environments but you can control everything from 1 single device.
As far AC2, it works but as indicated, it can become tricky space-wise ...
(actually: pure platform wise there is no difference between AC2 / cap ac / wap ac / cap XL ac)
