Add p2p_go_max_inactivity config option (UPSTREAM)

This enables setting a different max inactivity timeout for P2P GO.
This timeout is used to detect inactive clients. In some scenarios
it may be useful to have control over this and set a shorter timeout
than the default 300s. For example when running STA and P2P GO interfaces
concurrently, the STA interface may perform scans which may cause the
GO to miss a disassoc / deauth frames from a client and keep assuming
that the client is connected until the inactivity detection kicks in.
300 secs is a bit too long for such scenarios and creates a bad user
experience.

Signed-off-by: Eyal Shapira <eyal@wizery.com>

1 files changed, 11 insertions, 0 deletions

diff --git a/wpa_supplicant/config.h b/wpa_supplicant/config.h
index 8624e40..fd9ba78 100644
--- a/wpa_supplicant/config.h
+++ b/wpa_supplicant/config.h
@@ -18,6 +18,7 @@
 #define DEFAULT_FAST_REAUTH 1
 #define DEFAULT_P2P_GO_INTENT 7
 #define DEFAULT_P2P_INTRA_BSS 1
+#define DEFAULT_P2P_GO_MAX_INACTIVITY (5*60)
 #define DEFAULT_BSS_MAX_COUNT 200
 #define DEFAULT_BSS_EXPIRATION_AGE 180
 #define DEFAULT_BSS_EXPIRATION_SCAN_COUNT 2
@@ -680,6 +681,16 @@ struct wpa_config {
 	 */
 	struct wpabuf *wps_nfc_dev_pw;
 
+
+	/**
+	 * p2p_go_max_inactivity - Timeout in seconds to detect STA's inactivity
+	 *
+	 * This timeout value is used in P2P GO mode to clean up
+	 * inactive stations.
+	 * By default: 300 seconds.
+	 */
+	int p2p_go_max_inactivity;
+
 	/**
 	 * sched_scan_short_interval - Initial interval for sched scan in secs
 	 * sched scan will start with this interval for num_short_intervals