From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: attempt to scan fails (device busy) if essid/ssid was changed recently
Date: Tue, 07 Apr 2009 16:51:50 +0300 [thread overview]
Message-ID: <1239112310.15015.25.camel@maxim-laptop> (raw)
In-Reply-To: <1239110860.4084.0.camel@johannes.local>
On Tue, 2009-04-07 at 15:27 +0200, Johannes Berg wrote:
> On Tue, 2009-04-07 at 16:20 +0300, Maxim Levitsky wrote:
>
> > > Of course, we can go back to dropping the scan request, but that
> > > wouldn't be very nice.
> > >
> > > Is this creating any problems?
>
> > Yep, but dropping the request won't help ether.
>
> Indeed.
>
> > Problem is that wpa_supplicant will attempt to scan before association,
> > scan fails (it doesn't know it is already running) thus it waits 10
> > seconds. (I patched it to wait 2 seconds).
> >
> > It happens if user first disconnects, and then reconnects to a network
> > (typical test I do for time it takes to connect)
> >
> > Now I patched it not to clear essid on disconnect, and this helped
> > reduce connect times by about 2 seconds.
> >
> > now it takes just 3~4 seconds to connect to open network, and ~6 seconds
> > to WPA2 network.
> >
> > (This is with patched dhclient, I reduced its timeouts, but this is
> > another story.... it seems that first DHCPREQUEST never succeeds, and I
> > tested this with 2 cards, and few wireless networks)
>
> Have you tried with a new tree and wpa_supplicant's (from git) nl80211
> driver? Might be a lot better.
I use NM and wpa_supplicant from -git
Last time, I tried nl80211 wpa_supplicant driver it didn't work well,
but I try again soon I hope.
Best regards,
Maxim Levitsky
>
> johannes
next prev parent reply other threads:[~2009-04-07 13:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 0:00 attempt to scan fails (device busy) if essid/ssid was changed recently Maxim Levitsky
2009-04-07 8:18 ` Johannes Berg
2009-04-07 12:51 ` Maxim Levitsky
2009-04-07 12:56 ` Johannes Berg
2009-04-07 13:04 ` Maxim Levitsky
2009-04-07 13:13 ` Johannes Berg
2009-04-07 13:20 ` Maxim Levitsky
2009-04-07 13:27 ` Johannes Berg
2009-04-07 13:51 ` Maxim Levitsky [this message]
2009-04-07 20:24 ` Maxim Levitsky
2009-04-07 20:37 ` Johannes Berg
2009-04-10 20:30 ` Maxim Levitsky
2009-04-10 20:47 ` Maxim Levitsky
2009-04-11 11:35 ` Johannes Berg
2009-04-11 11:34 ` Johannes Berg
2009-04-11 23:55 ` Maxim Levitsky
2009-04-12 7:06 ` Johannes Berg
2009-04-12 12:49 ` Maxim Levitsky
2009-04-08 14:26 ` Dan Williams
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=1239112310.15015.25.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--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