As you mentioned, roaming only works within the same ROS instance, which means you need to have the same CAPsMAN controller for all your APs. Wifiwave2 interfaces in station mode do not support 802.11r, which is the fast transition protocol for roaming between APs. AC2 and AX2 are different wifi technologies and cannot be controlled by the same ROS instance, so you cannot roam between them.In wifiwave2 quite a bit of those requested parameters are not available (yet).
Roaming only works within the same ROS instance.
This means radios on the same AP, or radios controlled by the same CAPSMAN controller.
AC2 and AX2 are different wifi technologies and can not be controlled by the same ROS instance.
So you are actually comparing apples to oranges here ...
What you can do (no real roaming but to "guide" the change-over process a bit), is use access list to limit signal levels of a client device and actively kick it out when a certain threshold is reached.
Be aware though there are clients which do not respond too well to such behavior (i.e. they may try to avoid an AP doing that).
But do I understand correctly you are trying to use AX2 or AC2 as client ?
How do you move those ?
One possible workaround is to use access list to limit the signal levels of a client device and actively kick it out when a certain threshold is reached. This can force the client to switch to a better AP, but it may also cause some issues with some clients that do not like being disconnected. Another option is to use an EoIP tunnel or a L2VPN between the CAPsMAN controller and the CAPs, which can create a layer 2 bridge and allow roaming across different ROS instances.
If you are trying to use AX2 or AC2 as a client, you need to make sure that they support the wifiwave2 package and the roaming features. You also need to configure them to connect to the APs that have the same CAPsMAN controller. How you move them depends on your physical setup and your network topology.
Statistics: Posted by Jaxxon23 — Fri Feb 02, 2024 1:16 am