EAP: Clear ClientTimeout back to default value in INITIALIZE

This fixes an issue where WPS run leaves a small ClientTimeout
value (2) configured and the next EAPOL authentication is started
with that small value even for Identity exchange. This can cause
problems when an EAPOL packet gets dropped immediately after
association and a retry of that packet is needed (which may take
more than two seconds).

diff --git a/src/eap_peer/eap.c b/src/eap_peer/eap.c
index 39513d6a75aaec671d9332024965df3132cccd14..17d3574c05fe9d6543dbddc0728f9e4e633a1228 100644 (file)
--- a/src/eap_peer/eap.c
+++ b/src/eap_peer/eap.c
@@ -147,6 +147,7 @@ SM_STATE(EAP, INITIALIZE)
        sm->methodState = METHOD_NONE;
        sm->allowNotifications = TRUE;
        sm->decision = DECISION_FAIL;
+       sm->ClientTimeout = EAP_CLIENT_TIMEOUT_DEFAULT;
        eapol_set_int(sm, EAPOL_idleWhile, sm->ClientTimeout);
        eapol_set_bool(sm, EAPOL_eapSuccess, FALSE);
        eapol_set_bool(sm, EAPOL_eapFail, FALSE);