All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Jan Willies <jan@willies.info>
Cc: linux-wireless@vger.kernel.org
Subject: Re: 4965AGN loses connection on Custom wireless event
Date: Tue, 07 Jul 2009 11:21:03 -0400	[thread overview]
Message-ID: <1246980063.28570.1.camel@localhost.localdomain> (raw)
In-Reply-To: <4A535168.4050800@willies.info>

On Tue, 2009-07-07 at 15:45 +0200, Jan Willies wrote:
> Hi,
> 
> On 01.07.2009 16:29, Dan Williams wrote:
> > Jouni, how should the supplicant handle a WEXT assoc event for the AP
> > that's already associated with?  That seems to be what's going on here;
> > the card is coming back from a scan and emitting an assoc event (not
> > sure why) and that's making the supplicant (wrongly IMHO) try to reauth
> > at the EAP level for some reason.
> 
> Did I miss the answer here? Is there any more information I can provide?

Nope, not yet.  Jouni's traveling at the moment though so he might reply
when he gets back.

Dan



      reply	other threads:[~2009-07-07 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 13:04 4965AGN loses connection on Custom wireless event Jan Willies
2009-07-01 14:29 ` Dan Williams
2009-07-07 13:45   ` Jan Willies
2009-07-07 15:21     ` Dan Williams [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=1246980063.28570.1.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=jan@willies.info \
    --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.