Wireless access point daemon, patched with ubus support
143a4bf632
Windows XP and Vista clients can get confused about EAP-Identity/Request when they probe the network with EAPOL-Start. In such a case, they may assume the network is using IEEE 802.1X and prompt user for a certificate while the correct (non-WPS) behavior would be to ask for the static WEP key. As a workaround, use Microsoft Provisioning IE to advertise that legacy 802.1X is not supported. This seems to make Windows ask for a static WEP key when adding a new network, but at least Windows XP SP3 was still marking IEEE 802.1X enabled for the network. Anyway, this is better than just leaving the network configured with IEEE 802.1X and automatic WEP key distribution. |
||
|---|---|---|
| eap_example | ||
| hostapd | ||
| mac80211_hwsim | ||
| patches | ||
| radius_example | ||
| src | ||
| testing | ||
| wpa_supplicant | ||
| www | ||
| build_nsis.sh | ||
| build_release | ||
| COPYING | ||
| FAQ | ||
| 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).