config: make remote_node_timeout configurable

The logic for customizing the remote_node_timeout config option was
missing. The default value of 10 could not be altered by a user.

Add the required logic and a short explanation of the config-option to
the default configuration.

Signed-off-by: David Bauer <mail@david-bauer.net>
This commit is contained in:
David Bauer
2022-01-01 18:00:45 +01:00
parent 918b809d64
commit 5610aceea5
3 changed files with 5 additions and 1 deletions

View File

@@ -44,6 +44,9 @@ config usteer
# Interval (ms) between sending state updates to other APs
#option remote_update_interval 1000
# Number of remote update intervals after which a remote-node is deleted
#option remote_node_timeout 10
# Allow rejecting assoc requests for steering purposes (0/1)
#option assoc_steering 0

View File

@@ -77,7 +77,7 @@ uci_usteer() {
sta_block_timeout local_sta_timeout local_sta_update \
max_neighbor_reports max_retry_band seen_policy_timeout \
load_balancing_threshold band_steering_threshold \
remote_update_interval \
remote_update_interval remote_node_timeout\
min_connect_snr min_snr signal_diff_threshold \
initial_connect_delay roam_process_timeout\
roam_kick_delay roam_scan_tries \

1
ubus.c
View File

@@ -152,6 +152,7 @@ struct cfg_item {
_cfg(U32, load_balancing_threshold), \
_cfg(U32, band_steering_threshold), \
_cfg(U32, remote_update_interval), \
_cfg(U32, remote_node_timeout), \
_cfg(BOOL, assoc_steering), \
_cfg(I32, min_connect_snr), \
_cfg(I32, min_snr), \