-
Notifications
You must be signed in to change notification settings - Fork 19
Troubleshooting
Usteer does not resolve underlying infrastructure issues.
Ideally, access points should have only minimal coverage overlap, so WiFi transmit power should be optimized first .
There are several guides available for proper power tuning .
Without correct optimization, a client may connect to an AP that is far away .
All APs should have 802.11k/v/r enabled .
- Roaming
- Dynamic band steering
- Transition requests are enforced
- Start with the default configuration .
- The configuration should remain unchanged; adjust inter‑AP networking only if your LAN is insecure .
- Communication between APs is unencrypted and uses multicast traffic .
- Lower
roam_scan_snrif you want clients to stay longer on a weaker AP . - Clients roam only when a better AP is available above –65 dBm .
- If no suitable AP exists, the client remains connected — this is not a hard limit .
When a client moves from a strong 2.4 GHz signal to a weaker 5 GHz signal without roaming or band steering transition request
Probe steering causes usteer‑ng‑managed APs to ignore probe requests, effectively locking the client to its current AP.
The AP becomes invisible to the client, so there is no interruption.
Roaming only occurs if the target AP has a better rating .
Set the client’s aggressiveness to 1 to avoid ping‑pong behavior between bands . This allows the client to decide when to roam . Transition requests are treated as suggestions rather than enforced actions .
If band steering is used, increase the dynamic band steering interval to give the client more time before steering is attempted .