805e6dc663
There is not really much else the Authenticator can do if it does not receive valid EAP response from the Supplicant/EAP peer. EAP-Failure would need to be sent before trying to start again with EAP-Request/Identity, but that is not allowed before the EAP peer actually replies. Anyway, forcing a new association is likely to clean up peer state, too, so it can help fixing some issues that could have caused the peer not to be able to reply in the first place. |
||
|---|---|---|
| eap_example | ||
| hostapd | ||
| mac80211_hwsim | ||
| patches | ||
| radius_example | ||
| src | ||
| testing | ||
| wpa_supplicant | ||
| www | ||
| COPYING | ||
| FAQ | ||
| README | ||
| build_nsis.sh | ||
| build_release | ||
README
wpa_supplicant and hostapd v0.6.x --------------------------------- Copyright (c) 2002-2007, Jouni Malinen <j@w1.fi> and contributors All Rights Reserved. These program is dual-licensed under both the GPL version 2 and BSD license. Either license may be used at your option. This package may include either wpa_supplicant, hostapd, or both. See README file respective subdirectories (wpa_supplicant/README or hostapd/README) for more details. Source code files have been moved around in v0.6.x releases and compared to earlier releases, the programs are now build by first going to a subdirectory (wpa_supplicant or hostapd) and creating build configuration (.config) and running 'make' there (for Linux/BSD/cygwin builds).