I have two wAP ax devices (v7.17), and I need some guidance on setting up dual-band steering and seamless roaming using the new Qcom package (WiFi Wave 2). Specifically, I want to implement:
Dual-band steering: Automatically connecting a device to the 5GHz band when the signal is strong, and switching to 2GHz when the 5GHz signal drops below, for example, -70 dBm.
Roaming: Ensuring devices can switch seamlessly between the two wAPs as they move throughout the building.
The setup is as follows:
One wAP will be placed upstairs and the other downstairs.
I want to use a single SSID for both bands and both devices, allowing automatic switching between access points and bands.
I’ve managed to configure roaming between the two devices on the 5GHz band by adjusting the maximum power to 15 dBm for 2GHz and 25 dBm for 5GHz on both wAPs. However, devices don’t seem to switch to 2GHz automatically when needed.
This setup isn’t for me, and I don’t know much about the building it’s for, other than that it’s a two-floor building.
It’s not OK to force devices to roam to certain APs. The problem is that whatever is configured (including the whole 802.11 r/k/v), it’s still device which decides to move to another AP. The only difference between simply using same SSID and using the whole mobility suite is that in later case device gets some info about eligible BSSIDs (additional radios, part of same SSID) and some simplified handling on destination AP (e.g. reusing encryption keys). So it then still boils down to device preference (band, etc.). E.g. I’ve got a tablet (Huawei) which seems to prefer 2.4GHz band and AC over 5GHz and AX (but does work with such radio if “forced” to use it).
If you want to “force” devices somewhere, the end effect might be that device actually connects to preferred AP, but will get disconnected in the process (so disconnect/connect instead of roam-to). In this sense, reducing Tx power of 2GHz radios does serve the purpose (it makes those radios less attractive to devices) but at the same time it may be creating coverage gaps. So ideally you’d set Tx power of 2GHz radios so that they offer continuous coverage between APs (but only just … if there isn’t a very important place between APs which requires strong WiFi signal, such as toilet). And just accept that devices won’t always be using AP radio with highest capacity.
Indeed to get roaming between different APs one needs CAPsMAN up and running. But to get roaming between radios of same AP one doesn't need CAPsMAN, relatively default config should suffice.
For roaming to work seamlessly, you need to use capsman (and then in security / FT tab, settings for FT Enabled and FT over DS should be active).
If you do not have a capsman controller, there will be disconnects when clients move from AP A to AP B.
Using mentioned settings, roaming can work between radios of the same AP but not between APs without capsman controller.
But you can use one of the wAP AX devices as controller, they are powerful enough.
Is this something to consider ?
I thought CAPsMAN was primarily used for managing large networks with many access points, but I don’t know much about it. I see a lot of videos praising it, but I’m not sure how it could benefit me. Maybe I should look into it—idk
