From: Maxim Levitsky <maximlevitsky@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: attempt to scan fails (device busy) if essid/ssid was changed recently
Date: Tue, 07 Apr 2009 03:00:01 +0300 [thread overview]
Message-ID: <1239062401.4705.23.camel@maxim-laptop> (raw)
Recently I was trying to reduce time it takes for wireless card to
connect.
I noticed that always first attempt at scan fails when NM asks for scan.
I also noticed that this happens with quite recent kernels (I think
2,6.28) didn't have this behavior.
Looking a bit deeper I discovered that each time NM disconnects from a
networks it sets random ssid/essid to the card (using wireless
extensions)
After that scan fails for some time.
as a NM free example you can run
iwconfig wlan0 essid dummy
iwlist scan
and this will fail
NM in this case waits for whole 10 seconds.
What do you think about this?
I confirm that on iwl3945 and ath5k, so this isn't driver specific.
Best regards,
Maxim Levitsky
next reply other threads:[~2009-04-07 0:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 0:00 Maxim Levitsky [this message]
2009-04-07 8:18 ` attempt to scan fails (device busy) if essid/ssid was changed recently 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
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=1239062401.4705.23.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--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