From: Dan Williams <dcbw@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Jan Engelhardt <jengelh@medozas.de>, linux-wireless@vger.kernel.org
Subject: Re: Automatic reassociate with AP
Date: Fri, 15 May 2009 13:02:29 -0400 [thread overview]
Message-ID: <1242406949.10933.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20090515133359.GB2773@tuxdriver.com>
On Fri, 2009-05-15 at 09:33 -0400, John W. Linville wrote:
> On Fri, May 15, 2009 at 01:10:28PM +0200, Jan Engelhardt wrote:
>
> > when the AP flakes out, or I just appen to be out of range, the kernel
> > drops the AP association, as dmesg shows:
> >
> > wlan0: No ProbeResp from current AP 00:0b:0e:4f:cf:80 - assume out of
> > range
> >
> > Manually rerunning `iwconfig wlan0 essid FooNet channel 11`
> > reassociates, but I wonder whether the kernel could not do that itself,
> > given that it knows the previous settings like ESSID.
>
> Patches welcome... :-)
This does cause problems in some cases, at least for WEXT. iwl does
attempt to continually reassociate, and that results in some cases where
streams of disassoc events overwhelm userspace. The supplicant should
obviously get fixed here, but before doing something like this, we
should make sure that all the nl80211 calls are implemented to tell the
driver "Stop whatever you're doing and idle yourself". I've talked
about this with Johannes before so he may have already stuffed that into
nl80211 somewhere.
Dan
prev parent reply other threads:[~2009-05-15 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 11:10 Automatic reassociate with AP Jan Engelhardt
2009-05-15 13:33 ` John W. Linville
2009-05-15 17:02 ` 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=1242406949.10933.27.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=jengelh@medozas.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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