On Mon, Apr 09, 2007 at 04:52:09PM -0500, Larry Finger wrote: > logger: WPA: Sending EAPOL-Key 2/4 > > At this point, the two cases diverge. The bad example has a 4 second delay, > then I get the following: > > kernel: eth1: RX deauthentication from 00:14:bf:85:49:fa (reason=15) > kernel: eth1: deauthenticated > logger: WPA: TX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 09 00 20 00 > Do you know why the supplicant waits the 4 seconds between the "sending key > 2/4" message and the actual transmission of it? Do you think that is > important, or is it a false lead? I would appreciate any debugging leads > you might offer. This looks very odd.. There is not really any blocking operations in wpa_supplicant between the places that print "WPA: Sending EAPOL-Key 2/4" and "WPA: TX EAPOL-Key"... How do you generate these syslog messages? Could there be something buffering the TX EAPOL-Key message and the delay would actually happen only after that? This could be caused by send() getting blocked by something and the receiption of deauthentication triggering unblocking somehow.. -- Jouni Malinen PGP id EFC895FA - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
