diff options
author | Zhu Yi <yi.zhu@intel.com> | 2007-11-22 11:10:22 +0800 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2007-11-29 18:08:47 -0500 |
commit | a10605e599a7873417043fe2bb559abe719f8a1a (patch) | |
tree | 03447d2c1c0834289d6570e95445043630090615 /net/ieee80211 | |
parent | d9f8bcbf67a0ee67c8cb0734f003dfe916bb5248 (diff) | |
download | op-kernel-dev-a10605e599a7873417043fe2bb559abe719f8a1a.zip op-kernel-dev-a10605e599a7873417043fe2bb559abe719f8a1a.tar.gz |
mac80211: free ifsta->extra_ie and clear IEEE80211_STA_PRIVACY_INVOKED
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.
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).
On Wed, 2007-11-21 at 16:19 +0100, Johannes Berg wrote:
> Yeah. Can you amend the patch to also clear the
> IEEE80211_STA_PRIVACY_INVOKED flag?
Signed-off-by: Zhu Yi <yi.zhu@intel.com>
Acked-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/ieee80211')
0 files changed, 0 insertions, 0 deletions