All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jouni Malinen" <jkm@devicescape.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Jouni Malinen <j@w1.fi>, wireless <linux-wireless@vger.kernel.org>
Subject: Re: Problem with wpa_supplicant on bcm43xx-mac80211
Date: Mon, 9 Apr 2007 15:30:36 -0700	[thread overview]
Message-ID: <20070409223036.GJ22114@devicescape.com> (raw)
In-Reply-To: <461AB589.20405@lwfinger.net>

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

      reply	other threads:[~2007-04-09 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 21:52 Problem with wpa_supplicant on bcm43xx-mac80211 Larry Finger
2007-04-09 22:30 ` Jouni Malinen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070409223036.GJ22114@devicescape.com \
    --to=jkm@devicescape.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.