Probe suppression is mostly useful in high density deployments, where
all APs responding to all client probes would result in all channels
being saturated. It effectively hides APs from clients, and can cause
problems in normal density deployments.
Add an option for it, so it can be disabled.
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Acked-by: David Bauer <mail@david-bauer.net>
config.link_measurement_interval = 30000;
+ config.probe_steering = 1;
+
config.roam_kick_delay = 10000;
config.roam_process_timeout = 5 * 1000;
config.roam_scan_tries = 3;
# Allow rejecting assoc requests for steering purposes (0/1)
#option assoc_steering 0
+ # Allow ignoring probe requests for steering purposes (0/1)
+ #option probe_steering 1
+
# Minimum signal-to-noise ratio or signal level (dBm) to allow connections
#option min_connect_snr 0
int min_signal;
bool ret = true;
+ if (type == EVENT_TYPE_PROBE && !config.probe_steering)
+ goto out;
+
if (type == EVENT_TYPE_AUTH)
goto out;
uint32_t measurement_report_timeout;
bool assoc_steering;
+ bool probe_steering;
uint32_t max_neighbor_reports;