| commit | 68f2d02669f7102be80aae47155f45e18950d223 | |
| author | Jouni Malinen <jouni.malinen@atheros.com> | |
| Thu, 11 Jun 2009 15:19:45 +0000 (11 18:19 +0300) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Mon, 15 Jun 2009 19:05:51 +0000 (15 15:05 -0400) | ||
| tree | d62bac9654a823b14bebabf7f837e2f9acba2260 | treesnapshot (tar.gz zip) |
| parent | e1f8a19e6fc4f6d4267f6d3fe465553c3688f28e | commitdiff |
mac80211: Do not try to associate with an empty SSID
It looks like some programs (e.g., NM) are setting an empty SSID with
SIOCSIWESSID in some cases. This seems to trigger mac80211 to try to
associate with an invalid configuration (wildcard SSID) which will
result in failing associations (or odd issues, potentially including
kernel panic with some drivers) if the AP were to actually accept this
anyway).
Only start association process if the SSID is actually set. This
speeds up connection with NM in number of cases and avoids sending out
broken association request frames.
Signed-off-by: Jouni Malinen <jouni.malinen@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
It looks like some programs (e.g., NM) are setting an empty SSID with
SIOCSIWESSID in some cases. This seems to trigger mac80211 to try to
associate with an invalid configuration (wildcard SSID) which will
result in failing associations (or odd issues, potentially including
kernel panic with some drivers) if the AP were to actually accept this
anyway).
Only start association process if the SSID is actually set. This
speeds up connection with NM in number of cases and avoids sending out
broken association request frames.
Signed-off-by: Jouni Malinen <jouni.malinen@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| net/mac80211/mlme.c | diffblobblamehistory |