summaryrefslogtreecommitdiff
path: root/usr/Kconfig
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2013-07-31 11:23:06 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-08-20 08:43:03 -0700
commit7febdf14e427e1ed642f0a0c97182d50b6ce199e (patch)
tree96effc0044b63186542af1ca94df65ef8526ec46 /usr/Kconfig
parent5ae473da2f18b175b7ea794326523e485d6795a5 (diff)
downloadlinux-3.10-7febdf14e427e1ed642f0a0c97182d50b6ce199e.tar.gz
linux-3.10-7febdf14e427e1ed642f0a0c97182d50b6ce199e.tar.bz2
linux-3.10-7febdf14e427e1ed642f0a0c97182d50b6ce199e.zip
mac80211: ignore HT primary channel while connected
commit 5cdaed1e878d723d56d04ae0be1738124acf9f46 upstream. While we're connected, the AP shouldn't change the primary channel in the HT information. We checked this, and dropped the connection if it did change it. Unfortunately, this is causing problems on some APs, e.g. on the Netgear WRT610NL: the beacons seem to always contain a bad channel and if we made a connection using a probe response (correct data) we drop the connection immediately and can basically not connect properly at all. Work around this by ignoring the HT primary channel information in beacons if we're already connected. Also print out more verbose messages in the other situations to help diagnose similar bugs quicker in the future. Acked-by: Andy Isaacson <adi@hexapodia.org> Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'usr/Kconfig')
0 files changed, 0 insertions, 0 deletions