From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Zhu Yi <yi.zhu@intel.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: free ifsta->extra_ie in ieee80211_stop
Date: Tue, 20 Nov 2007 11:25:22 -0500 [thread overview]
Message-ID: <1195575922.3389.20.camel@localhost.localdomain> (raw)
In-Reply-To: <1195565876.10920.29.camel@johannes.berg>
On Tue, 2007-11-20 at 14:37 +0100, Johannes Berg wrote:
> On Tue, 2007-11-20 at 14:55 +0800, Zhu Yi wrote:
> > I'm not sure if this is best choice, someone might have better
> > solutions. But this patch fixed the connection problem when switching
> > from a WPA enabled AP (using wpa_supplicant) to an open AP (using
> > iwconfig). The root cause is when we connect to a WPA enabled AP,
> > wpa_supplicant sets the ifsta->extra_ie thru SIOCSIWGENIE. But if we
> > stop wpa_supplicant and connect to an open AP with iwconfig, there is
> > no way to clear the extra_ie so that mac80211 keeps connecting with that.
>
> Fun.
>
> > Someone could argue wpa_supplicant should clear the extra_ie during
> > its shutdown. But mac80211 should also handle the unexpected shutdown
> > case (ie. killall -9 wpa_supplicant).
>
> Yes. But if you do that, the interface won't be down either. Maybe this
> should also be done when removing keys?
That seems better to me; although couldn't it also be cleared when
setting static WEP keys? Dynamic WEP shouldn't care about the IE bits
either, so any time a WEP key is set and you're _not_ doing WPA the IE
could get cleared.
Though on the other hand, the interface isn't going to work much longer
after wpa_supplicant goes away anyway, depending on how long the
group/multicast rekey interval is.
Dan
next prev parent reply other threads:[~2007-11-20 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 6:55 [PATCH] mac80211: free ifsta->extra_ie in ieee80211_stop Zhu Yi
2007-11-20 13:37 ` Johannes Berg
2007-11-20 16:25 ` Dan Williams [this message]
2007-11-20 16:31 ` Johannes Berg
2007-11-21 3:17 ` Zhu Yi
2007-11-21 15:19 ` Johannes Berg
2007-11-22 3:10 ` Zhu Yi
2007-11-22 12:59 ` 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=1195575922.3389.20.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=yi.zhu@intel.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;
as well as URLs for NNTP newsgroup(s).