#633: WPA-PSK broken because of r1553 ?
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: dyqith
Type: defect | Status: new
Priority: major | Milestone: version 0.9.x -
progressive release candidate phase
Component: madwifi: 802.11 stack | Version: trunk
Resolution: | Keywords:
Patch_attached: 0 |
----------------------------------------+-----------------------------------
Comment (by [EMAIL PROTECTED]):
Today I had the similar "EAPOL-Key timeout" problem and solved it the
following way:
1. Switched on Wi-Fi and selected required network (WPA-PSK).
2. PPC failed to connect to it with EAPOL-Key timeout message.
3. Toggled wireless network off and on. After turning Wi-Fi on, PPC
automatically started to connect to the required network (since it is
first in the list of preferred networks).
4. PPC successfully connected to the first network - and this was the
network required.
However, sometimes this does not help and PPC connects to other network
instead the selected (and it is very difficult to "switch" it from one VAP
to another, by the way).
In general, I've noted that PPC's (at least WM 2003 SE based ones) have
very, very strange and almost unpredictable wireless networking.
Especially in case there are several wireless networks around.
P.S. Hostapd 0.5.3 did not worked for me too (EAPOL-Key timeout), but
madwifi 1590+hostapd 0.4.7 works.
--
Ticket URL: <http://madwifi.org/ticket/633>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
