Searched hist:"7 d930bc3" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/net/wireless/ |
H A D | mlme.c | 7d930bc3 Tue Oct 20 01:08:53 CDT 2009 Johannes Berg <johannes@sipsolutions.net> cfg80211: sme: deauthenticate on assoc failure
When the in-kernel SME gets an association failure from the AP we don't deauthenticate, and thus get into a very confused state which will lead to warnings later on. Fix this by actually deauthenticating when the AP indicates an association failure.
(Brought to you by the hacking session at Kernel Summit 2009 in Tokyo, Japan. -- JWL)
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com> 7d930bc3 Tue Oct 20 01:08:53 CDT 2009 Johannes Berg <johannes@sipsolutions.net> cfg80211: sme: deauthenticate on assoc failure When the in-kernel SME gets an association failure from the AP we don't deauthenticate, and thus get into a very confused state which will lead to warnings later on. Fix this by actually deauthenticating when the AP indicates an association failure. (Brought to you by the hacking session at Kernel Summit 2009 in Tokyo, Japan. -- JWL) Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | sme.c | 7d930bc3 Tue Oct 20 01:08:53 CDT 2009 Johannes Berg <johannes@sipsolutions.net> cfg80211: sme: deauthenticate on assoc failure
When the in-kernel SME gets an association failure from the AP we don't deauthenticate, and thus get into a very confused state which will lead to warnings later on. Fix this by actually deauthenticating when the AP indicates an association failure.
(Brought to you by the hacking session at Kernel Summit 2009 in Tokyo, Japan. -- JWL)
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | core.h | 7d930bc3 Tue Oct 20 01:08:53 CDT 2009 Johannes Berg <johannes@sipsolutions.net> cfg80211: sme: deauthenticate on assoc failure
When the in-kernel SME gets an association failure from the AP we don't deauthenticate, and thus get into a very confused state which will lead to warnings later on. Fix this by actually deauthenticating when the AP indicates an association failure.
(Brought to you by the hacking session at Kernel Summit 2009 in Tokyo, Japan. -- JWL)
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|