diff options
author | Daniel Drake <dsd@gentoo.org> | 2007-07-10 19:32:11 +0200 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2007-07-12 16:07:26 -0400 |
commit | 63fc33ceb0ccc08b3f62d7bfe56a33eb33ca9427 (patch) | |
tree | 6fb60af08616b2f4065cdd74b83f43c819f1853c /Documentation/networking | |
parent | 5628221caf88e2a052782b042e12da7cd34111b0 (diff) | |
download | kernel_samsung_smdk4412-63fc33ceb0ccc08b3f62d7bfe56a33eb33ca9427.zip kernel_samsung_smdk4412-63fc33ceb0ccc08b3f62d7bfe56a33eb33ca9427.tar.gz kernel_samsung_smdk4412-63fc33ceb0ccc08b3f62d7bfe56a33eb33ca9427.tar.bz2 |
[PATCH] mac80211: improved 802.11g CTS protection
Currently, CTS protection is partially implemented twice:
1. via prism2 ioctls, only used by hostapd
2. via STA beacon parsing, recorded in sta.use_protection but never used
(other than printed in debugfs)
Protection control should be implemented on a per-subif basis. For example,
a single physical device may be running a soft AP on one channel, and a STA
on another. The AP interface should use protection based on what hostapd told
it, and the STA interface should use protection based on beacon parsing.
These should operate independantly: one subif using protection should not
influence the other.
To implement this, I moved the use_protection flag into ieee80211_sub_if_data
and removed the device-global cts_protect_erp_frames flag.
I also made the PRISM2_PARAM_CTS_PROTECT_ERP_FRAMES write operation only
available for AP interfaces, to avoid any possibility of the user messing with
the behaviour of a STA.
Signed-off-by: Daniel Drake <dsd@gentoo.org>
Signed-off-by: Jiri Benc <jbenc@suse.cz>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'Documentation/networking')
0 files changed, 0 insertions, 0 deletions