policy: add min_snr_kick_delay
Currently the min_snr option will result in kicking clients the first time their SNR dips below. This might not be desirable, as drivers (notably ath10k) sometimes report a much lower RSSI for a short timeframe after returning to sensible values. Also, a device might be in the process of roaming just to be kicked before. Add the min_snr_kick_delay option. A client will be kicked after this timeframe when it's SNR is below the min_snr threshold value over the complete timeframe. Signed-off-by: David Bauer <mail@david-bauer.net>
This commit is contained in:
@@ -56,6 +56,9 @@ config usteer
|
||||
# Minimum signal-to-noise ratio or signal level (dBm) to remain connected
|
||||
#option min_snr 0
|
||||
|
||||
# Timeout after which a station with snr < min_snr will be kicked
|
||||
#option min_snr_kick_delay 5000
|
||||
|
||||
# Timeout (in ms) after which a association following a disassociation is not seen
|
||||
# as a roam
|
||||
#option roam_process_timeout 5000
|
||||
|
||||
@@ -78,7 +78,7 @@ uci_usteer() {
|
||||
max_neighbor_reports max_retry_band seen_policy_timeout \
|
||||
load_balancing_threshold band_steering_threshold \
|
||||
remote_update_interval remote_node_timeout\
|
||||
min_connect_snr min_snr signal_diff_threshold \
|
||||
min_connect_snr min_snr min_snr_kick_delay signal_diff_threshold \
|
||||
initial_connect_delay roam_process_timeout\
|
||||
roam_kick_delay roam_scan_tries roam_scan_timeout \
|
||||
roam_scan_snr roam_scan_interval \
|
||||
|
||||
Reference in New Issue
Block a user