policy: add roam-scan timeout
Add an optional timeout when a better roaming candidate is not found after the scan-retry limit. The roam state-machine will not retry scanning before this timeout has expired. If the timeout is set to 0, the client is kicked instead, which resembles the behavior prior this commit. This is added, as without this patch, if a forced disconnect is not desired before roam_scan_trigger is exceeded the client will repeatedly be asked to return active beacon-reports. For battery powered clients this can result in a noticeable battery drain. Signed-off-by: David Bauer <mail@david-bauer.net>
This commit is contained in:
2
usteer.h
2
usteer.h
@@ -172,6 +172,7 @@ struct usteer_config {
|
||||
uint32_t roam_process_timeout;
|
||||
|
||||
uint32_t roam_scan_tries;
|
||||
uint32_t roam_scan_timeout;
|
||||
uint32_t roam_scan_interval;
|
||||
|
||||
int32_t roam_trigger_snr;
|
||||
@@ -229,6 +230,7 @@ struct sta_info {
|
||||
uint64_t roam_event;
|
||||
uint64_t roam_kick;
|
||||
uint64_t roam_scan_done;
|
||||
uint64_t roam_scan_timeout_start;
|
||||
|
||||
int kick_count;
|
||||
|
||||
|
Reference in New Issue
Block a user