From: Maxim Levitsky <maximlevitsky@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: commit #1868cf308a3b3a336fcfe52c5aea4ac12d5e42ac breaks wireless on my system
Date: Sat, 30 May 2009 23:47:17 +0300 [thread overview]
Message-ID: <1243716437.26585.4.camel@maxim-laptop> (raw)
I use nl80211 wpa_suppicant driver.
With this commit (have just bisected) I can't connect to same AP twice,
and usually only a module reload, or somtimes restart of supplicant
help.
Actually usually I can't connect again after first successful connection
at all.
With wext supplicant works, but still sometimes hangs in same way.
commit 1868cf308a3b3a336fcfe52c5aea4ac12d5e42ac
Author: Johannes Berg <johannes@sipsolutions.net>
Date: Tue May 19 22:16:25 2009 +0200
mac80211: don't try to do anything on unchanged genIE
When the genIE hasn't changed there's no reason to kick
the state machine since it won't be able to do anything
new -- doing this decreases the useless work we do for
reassociating because if we do kick the state machine
it will try to find a usable BSS but there might not be
one because wpa_supplicant will only change the BSSID
a little later.
In a sense this is a workaround for userspace behaviour,
but on the other hand userspace cannot really keep track
of what the kernel currently has for genIE since any
process could have changed that while wpa_supplicant
wasn't looking.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Best regards,
Maxim Levitsky
next reply other threads:[~2009-05-30 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 20:47 Maxim Levitsky [this message]
2009-05-30 20:49 ` commit #1868cf308a3b3a336fcfe52c5aea4ac12d5e42ac breaks wireless on my system Johannes Berg
2009-05-30 20:59 ` Maxim Levitsky
2009-05-30 22:37 ` Maxim Levitsky
2009-05-31 10:11 ` Johannes Berg
2009-05-31 12:03 ` Maxim Levitsky
2009-05-31 12:41 ` Maxim Levitsky
2009-06-01 7:29 ` Kalle Valo
2009-05-30 21:00 ` Larry Finger
2009-05-30 21:04 ` Johannes Berg
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=1243716437.26585.4.camel@maxim-laptop \
--to=maximlevitsky@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