1. 15 7月, 2008 1 次提交
    • J
      mac80211: make master netdev handling sane · 3e122be0
      Johannes Berg 提交于
      Currently, almost every interface type has a 'bss' pointer
      pointing to BSS information. This BSS information, however,
      is for a _local_ BSS, not for the BSS we joined, so having
      it on a STA mode interface makes little sense, but now they
      have it pointing to the master device, which is an AP mode
      virtual interface. However, except for some bitrate control
      data, this pointer is only used in AP/VLAN modes (for power
      saving stations.)
      
      Overall, it is not necessary to even have the master netdev
      be a valid virtual interface, and it doesn't have to be on
      the list of interfaces either.
      
      This patch changes the master netdev to be special, it now
       - no longer is on the list of virtual interfaces, which
         lets me remove a lot of tests for that
       - no longer has sub_if_data attached, since that isn't used
      
      Additionally, this patch changes some vlan/ap mode handling
      that is related to these 'bss' pointers described above (but
      in the VLAN case they actually make sense because there they
      point to the AP they belong to); it also adds some debugging
      code to IEEE80211_DEV_TO_SUB_IF to validate it is not called
      on the master netdev any more.
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      3e122be0
  2. 22 5月, 2008 1 次提交
  3. 08 5月, 2008 1 次提交
  4. 09 4月, 2008 2 次提交
  5. 02 4月, 2008 2 次提交
  6. 07 3月, 2008 1 次提交
  7. 01 3月, 2008 1 次提交
  8. 29 1月, 2008 4 次提交
  9. 11 10月, 2007 5 次提交
  10. 07 8月, 2007 1 次提交
  11. 18 7月, 2007 1 次提交
  12. 13 7月, 2007 1 次提交
    • D
      [PATCH] mac80211: improved 802.11g CTS protection · 63fc33ce
      Daniel Drake 提交于
      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: NDaniel Drake <dsd@gentoo.org>
      Signed-off-by: NJiri Benc <jbenc@suse.cz>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      63fc33ce
  13. 06 5月, 2007 1 次提交