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).
This commit is contained in:
Jouni Malinen 2011-10-18 18:44:35 +03:00 committed by Jouni Malinen
parent ed3eecd786
commit 54e9c5fc69

View file

@ -147,6 +147,7 @@ SM_STATE(EAP, INITIALIZE)
sm->methodState = METHOD_NONE; sm->methodState = METHOD_NONE;
sm->allowNotifications = TRUE; sm->allowNotifications = TRUE;
sm->decision = DECISION_FAIL; sm->decision = DECISION_FAIL;
sm->ClientTimeout = EAP_CLIENT_TIMEOUT_DEFAULT;
eapol_set_int(sm, EAPOL_idleWhile, sm->ClientTimeout); eapol_set_int(sm, EAPOL_idleWhile, sm->ClientTimeout);
eapol_set_bool(sm, EAPOL_eapSuccess, FALSE); eapol_set_bool(sm, EAPOL_eapSuccess, FALSE);
eapol_set_bool(sm, EAPOL_eapFail, FALSE); eapol_set_bool(sm, EAPOL_eapFail, FALSE);