summaryrefslogtreecommitdiffstats
path: root/drivers/dio
diff options
context:
space:
mode:
authorLuis R. Rodriguez <lrodriguez@atheros.com>2009-01-30 09:08:29 -0800
committerJohn W. Linville <linville@tuxdriver.com>2009-02-09 15:03:45 -0500
commit47f4d8872ffc57ad92d0fb344e677d12acc34acd (patch)
tree79213744d1d4ff3a97de1bfa475300db29822024 /drivers/dio
parent7230645e329b4a9c566fefa9327eb8734c7d392c (diff)
downloadkernel-crypto-47f4d8872ffc57ad92d0fb344e677d12acc34acd.tar.gz
kernel-crypto-47f4d8872ffc57ad92d0fb344e677d12acc34acd.tar.xz
kernel-crypto-47f4d8872ffc57ad92d0fb344e677d12acc34acd.zip
mac80211: do not TX injected frames when not allowed
Monitor mode is able to TX by using injected frames. We should not allow injected frames to be sent unless allowed by regulatory rules. Since AP mode uses a monitor interfaces to transmit management frames we have to take care to not break AP mode as well while resolving this. We can deal with this by allowing compliant APs solutions to inform mac80211 if their monitor interface is intended to be used for an AP by setting a cfg80211 flag for the monitor interface. hostapd, for example, currently does its own checks to ensure AP mode is not used on channels which require radar detection. Once such solutions are available it can can add this flag for monitor interfaces. Acked-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/dio')
0 files changed, 0 insertions, 0 deletions