Hello!

My CAPsMAN server runs on a v6 device. Is it possible to bind a v7 device as a CAPsMAN client to this v6 server?

In v6 the device which were handed over to CAPsMAN have to been explicitly specified (interface in the CAP card). I can't find that within the v7.

Any hints are welcome!


BR Holger

What exactely do you mean by V7 device? The "real" difference is being either a wifiwave2 device...or not.

You can run ROS7 using legacy wifi.

Wifiwave2 however, as indicated, is a totally different beast. That one can not be mixed with legacy wifi devices nor legacy capsman.

Hello!

I did some tests with different hardware an ROS v7.11.2

- hexS
- hap ac2
- hap ax3

hexS with wifiwave2 package works as a CAPsManger with the hap ax3 (which uses wifiwave2).
hap ac2 does not connect as a CAP to the hexS in this configuration
hap ac2 does not accept the wifiwave2 package (not installable)
hap ax3 without wifiwave2 doesn't have any wifi interface (no legacy mode possible)

at the end of the day the message is: it is impossible to connect legacy and wifiwave2 CAPs to one CAPsManager. is that correct?`

in other words: I have to upgrade all AP to wifiwave2 devices.

Sorry, that is a really bad policy by mikrotik and it is worth to think over using mikrotik at all. the big advantage using mikrotik is gone.... sorry.

BR Holger

at the end of the day the message is: it is impossible to connect legacy and wifiwave2 CAPs to one CAPsManager. is that correct?`

Yes, this is correct and they never made a secret about it.
This was known from day 1 capsman for wifiwave2 came out.

Sorry, that is a really bad policy by mikrotik and it is worth to think over using mikrotik at all. the big advantage using mikrotik is gone.... sorry.

We are not using a steam engine as main motor anymore either for most applications, do we ?
One day or the other Mikrotik HAD to move away from legacy wifi.
The launch of AX devices opened that door. But all AX devices (and AC3 which can be upgraded to wifiwave2) use one single version of capsman controller.
So that argument about 1 controller still holds if you make abstraction between legacy and wifiwave2 devices.

You still CAN use TWO capsman controllers within the same network during transition.
One for legacy wifi devices, one for wifiwave2 devices.
You do not HAVE to change everything at once (but personally I would consider it given wifiwave2 under capsman control is quite a bit better then legacy wifi capsman environment, my view).

Ok. I will send back the hap ax3. based on that the device is useless for me.

I have to think over how to deal with wifi in the future. Mikrotik won't be considered. Shame on u if u fool me once, shame on me if u fool me twice I dislike hard breaks without any backward compatibility for an entire periode