From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Charles Gordon <digigordo@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: iwlist wlan0 scan disrupts communications
Date: Wed, 28 Oct 2009 08:48:40 -0700 [thread overview]
Message-ID: <1256744920.3850.28.camel@localhost.localdomain> (raw)
In-Reply-To: <1256743398.4237.114.camel@johannes.local>
On Wed, 2009-10-28 at 16:23 +0100, Johannes Berg wrote:
> On Wed, 2009-10-28 at 11:02 -0400, Charles Gordon wrote:
>
> > I think that when the scan completes, mac80211 should either notify
> > wpa_supplicant that it should reassociate, or maybe send a null-data
> > frame to the AP which might cause it to send another
> > deauthentication/dissassociation frame (if we lost the connect).
>
> it does send nullfunc frames, you're probably running into an old bug
> that caused those to not be sent.
Correct, 2.6.28 did *not* have the nullfunc TX fix, so if the scan lasts
more than a few seconds, and the AP has traffic for the STA the TX will
time out, and the AP may drop the STA during the scan. 2.6.29 was the
first kernel that had the nullfunc TX fix.
But the supplicant should still reconnect...
Dan
next prev parent reply other threads:[~2009-10-28 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 20:40 iwlist wlan0 scan disrupts communications Charles Gordon
2009-10-27 20:43 ` Johannes Berg
2009-10-28 14:47 ` Charles Gordon
2009-10-28 14:54 ` Johannes Berg
2009-10-28 15:02 ` Charles Gordon
2009-10-28 15:23 ` Johannes Berg
2009-10-28 15:48 ` Dan Williams [this message]
2009-10-27 20:59 ` John W. Linville
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=1256744920.3850.28.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=digigordo@gmail.com \
--cc=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).