Hi,
in the past I had some good experience with defining access lists for signal strength in my capsman setup so that CAPs kicked out devices when the signal was getting really weak to help move them to another closer AP.
Now I switched to the new wifi with better roaming support for some devices but still have an RB4011 which runs the older wireless (because the incomplete support from wifi-qcom-ac).
When I switched I removed the access restrictions but then when a device gets closer to the RB4011 it was very eagerly connected to the primary capsman wifi even if there was no useful connection anymore (like -89).
So I re-introduced the access list to let the wifiwave network kick the device to connect to the RB4011.
This seems to work in general but I have the feeling that roaming within the wifiwave is somewhat less well working.
Here is an example from the logs:
AA:70:F8:8A:AC:8C@eg-2g roamed to AA:70:F8:8A:AC:8C@eg-5g, signal strength -86
AA:70:F8:8A:AC:8C@eg-5g disconnected, too weak signal, signal strength -85
I somewhat understand why 5G is preferred over 2G but roaming to a signal of -86 sounds like a bad idea? At least my access list does not allow that. Now in the worst case this game is going on for a while making the wifi unusable.
So my question is:
If access lists (which were somewhat common practice to use) are "bad" for wave2 is there another proposal how I can improve the "roaming" to the non-roaming wifi?
Any ideas, hints, feedback?
Thanks,
Wolfgang
in the past I had some good experience with defining access lists for signal strength in my capsman setup so that CAPs kicked out devices when the signal was getting really weak to help move them to another closer AP.
Now I switched to the new wifi with better roaming support for some devices but still have an RB4011 which runs the older wireless (because the incomplete support from wifi-qcom-ac).
When I switched I removed the access restrictions but then when a device gets closer to the RB4011 it was very eagerly connected to the primary capsman wifi even if there was no useful connection anymore (like -89).
So I re-introduced the access list to let the wifiwave network kick the device to connect to the RB4011.
This seems to work in general but I have the feeling that roaming within the wifiwave is somewhat less well working.
Here is an example from the logs:
AA:70:F8:8A:AC:8C@eg-2g roamed to AA:70:F8:8A:AC:8C@eg-5g, signal strength -86
AA:70:F8:8A:AC:8C@eg-5g disconnected, too weak signal, signal strength -85
I somewhat understand why 5G is preferred over 2G but roaming to a signal of -86 sounds like a bad idea? At least my access list does not allow that. Now in the worst case this game is going on for a while making the wifi unusable.
So my question is:
If access lists (which were somewhat common practice to use) are "bad" for wave2 is there another proposal how I can improve the "roaming" to the non-roaming wifi?
Any ideas, hints, feedback?
Thanks,
Wolfgang
Statistics: Posted by woro — Tue Feb 20, 2024 12:46 am