diff options
author | Emmanuel Grumbach <emmanuel.grumbach@intel.com> | 2014-03-04 14:50:13 (GMT) |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2014-03-19 20:29:56 (GMT) |
commit | 3afc2167f60a327a2c1e1e2600ef209a3c2b75b7 (patch) | |
tree | 2588b9503edc6b574126f54eee64ccb00aceb863 /block | |
parent | 2316d7b0544c4601cc852c801c93d1f451378740 (diff) | |
download | linux-3afc2167f60a327a2c1e1e2600ef209a3c2b75b7.tar.xz |
cfg80211/mac80211: ignore signal if the frame was heard on wrong channel
On 2.4Ghz band, the channels overlap since the delta
between different channels is 5Mhz while the width of the
receiver is 20Mhz (at least).
This means that we can hear beacons or probe responses from
adjacent channels. These frames will have a significant
lower RSSI which will feed all kinds of logic with inaccurate
data. An obvious example is the roaming algorithm that will
think our AP is getting weak and will try to move to another
AP.
In order to avoid this, update the signal only if the frame
has been heard on the same channel as the one advertised by
the AP in its DS / HT IEs.
We refrain from updating the values only if the AP is
already in the BSS list so that we will still have a valid
(but inaccurate) value if the AP was heard on an adjacent
channel only.
To achieve this, stop taking the channel from DS / HT IEs
in mac80211. The DS / HT IEs is taken into account to
discard the frame if it was received on a disabled channel.
This can happen due to the same phenomenon: the frame is
sent on channel 12, but heard on channel 11 while channel
12 can be disabled on certain devices. Since this check
is done in cfg80211, stop even checking this in mac80211.
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
[remove unused rx_freq variable]
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions