From bbed23aee6d963ba2f09fe988e6b1ad90a1ae2ff Mon Sep 17 00:00:00 2001 From: Brendan Jackman Date: Fri, 5 Apr 2019 12:36:42 +0000 Subject: [PATCH] hostapd: Reduce minimum beacon interval from 15 to 10 TUs Very short beacon intervals can be useful for certain scenarios such as minimising association time on PBSSs. Linux supports a minimum of 10[1] so let's reduce the minimum to match that. [1] https://elixir.bootlin.com/linux/latest/ident/cfg80211_validate_beacon_int Signed-off-by: Brendan Jackman --- hostapd/config_file.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/hostapd/config_file.c b/hostapd/config_file.c index ee3ae65f3..42f3b40ef 100644 --- a/hostapd/config_file.c +++ b/hostapd/config_file.c @@ -3136,9 +3136,10 @@ static int hostapd_config_fill(struct hostapd_config *conf, * cause problems with the current implementation. * Since it is unlikely that this small numbers are * useful in real life scenarios, do not allow beacon - * period to be set below 15 TU. */ - if (val < 15 || val > 65535) { - wpa_printf(MSG_ERROR, "Line %d: invalid beacon_int %d (expected 15..65535)", + * period to be set below 10 TU. */ + if (val < 10 || val > 65535) { + wpa_printf(MSG_ERROR, + "Line %d: invalid beacon_int %d (expected 10..65535)", line, val); return 1; }