We’ve two cAP ac’s serving WiFi for the house (amongst other things), they’re CAPsMAN managed from an RB2011, and we have several SSIDs terminating on several bridges.
For one particular SSID (well two SSIDs, one for 2GHz, one for 5GHz) I have roaming between the two cAP ac’s setup by way of an access control rule that boots any client that has an RSSI worse than -70 (accept rule -70..120, reject rule -120..-71). Works perfectly on 2.4GHz, I’m able to freely roam from one AP to the other with no issue (and also out to a cAP lite in the garage).
On 5.8GHz on the other hand I’ve run into issues.
Same Configuration is applied to the 5GHz cap on each of the access points.
Same Access Control rule is applied to them.
Both caps are bound to the same bridge (also the bridge the 2.4GHz SSIDs terminate on).
The “second” cAP refuses to authenticate a client on that (5GHz) SSID, the Android phone I’m testing with reports “The Password May Be Incorrect” which is obviously not the case since I’m able to connect to the other AP without issue and they have the same Configuration applied.
Is there something additional in the config parameters for a 5GHz radio that I’m missing which might be causing this?
As a sidenote, prior to getting the second cAP ac I attempted to run a Groove ac as a stopgap (happened to have a couple lying around), and had the same issue trying to roam on 5GHz.
I have two cap ACs at my place as well with the router being the RB450Gx4. No capsman yet as it was easy to play with both and learn setups that way. For small scale I dont see the need nor desire the extra complication and CPU overhead for running another network/infrastructure. In any case, just wanted to post to let you know that the 5Ghz network is not going to have the same ranges as the 2.4 and thus you will more than likely need to adjust your sensitivity settings for better roaming success (accept reject rules etc…)
Yeah, I’m aware that 2GHz vs 5GHz will have different ranges but I doubt that’s the issue here, since the phone won’t authenticate to the 5G SSID even when it’s sitting directly on top of the “second” cAP ac.
As an experiment I disabled the 5GHz radio in the “first” cAP and I still can’t authenticate on the “second” AP, so it seems something in the config that is being pushed by CAPsMAN isn’t quite right.
Might have to do some testing using a platform that will give me better feedback…