EAPOL Key Timeout 1/4

Daniel Rönnqvist kdronnqvist
Thu Oct 15 02:18:43 PDT 2009

2009/10/14 Jouni Malinen <j at w1.fi>:
> On Wed, Oct 14, 2009 at 09:11:00AM +0200, Daniel R?nnqvist wrote:
>> * Is hostapd from git supposed to work with nl80211 (with a bcm4306 rev3)?
> I don't know about bcm4306, but at least the current snapshot of hostapd
> seems to be working fine with the ath9k driver.
>> * What does "deauthenticated due to local death" mean?
> It means that hostapd requested a station to be deauthenticated (in this
> case, I would assume it happened due to the WPA 4-way handshake timing
> out).
>> * The only messages i see with tshark during the authentication
>> process is "EAPOL Key" and some "LLC" messages coming from the client
>> MAC. The hostapd log says EAPOL Key Timeout on handshake 1/4. Is this
>> enough to guess what ballpark my problem is in?
> Have you verified that your client is receiving the EAPOL-Key message
> 1/4 and replying with 2/4?
> --
> Jouni Malinen                                            PGP id EFC895FA

I see EAPOL key coming in on the client and it is answering to the
correct MAC address, but the AP is always just saying EAPOL key
timeout on 1/4. On the AP side i do "tshark -i wlan0" and see the
EAPOL key going out but nothing is coming back. However, I am reading
up on the subject because as of now I must admit that I do not know
how this works. I should be able to give a better description of my
problem in a week or so (after becoming junior guru of wifi) :) I did
get this setup to work before but after upgrading to Debian testing it
just wont.


More information about the Hostap mailing list