path: root/wpa_supplicant/dbus
diff options
authorJouni Malinen <jouni@qca.qualcomm.com>2013-09-26 18:24:09 (GMT)
committerJouni Malinen <j@w1.fi>2013-09-26 18:24:09 (GMT)
commitbbc6c729a58897e9265d53d53677b3ddeda4ff94 (patch)
tree8b369d4ec386c5a7c83adfdfda8f05e4ea07d131 /wpa_supplicant/dbus
parent41f853235fe1d1fad1acecc0ee5dfe81c872c6b2 (diff)
P2P: Use group formation timeout on persistent group GO
Previously, GO considered the group to be fully re-invoked after starting beaconing on successful invitation exchange. This would leave the group running until idle timeout (which may not be enabled) or explicit removal if the client fails to connect for any reason. Since the client is expected to connect immediately after the invitation exchange that ends with status=0 (i.e., either client initiated the exchange or it responded with success), extend group formation timeout to cover that period until the first successfully completed data connection. This allows the GO to remove the group automatically if the client devices does not connect within P2P_MAX_INITIAL_CONN_WAIT_GO_REINVOKE (15) seconds. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
Diffstat (limited to 'wpa_supplicant/dbus')
1 files changed, 1 insertions, 1 deletions
diff --git a/wpa_supplicant/dbus/dbus_new_handlers_p2p.c b/wpa_supplicant/dbus/dbus_new_handlers_p2p.c
index 6ec96df..52b36b4 100644
--- a/wpa_supplicant/dbus/dbus_new_handlers_p2p.c
+++ b/wpa_supplicant/dbus/dbus_new_handlers_p2p.c
@@ -347,7 +347,7 @@ DBusMessage * wpas_dbus_handler_p2p_group_add(DBusMessage *message,
goto inv_args;
if (wpas_p2p_group_add_persistent(wpa_s, ssid, 0, freq, 0,
- NULL)) {
+ NULL, 0)) {
reply = wpas_dbus_error_unknown_error(
"Failed to reinvoke a persistent group");