freebsd-skq/sys/net80211
sam b024266b89 fix adhoc/ibss operation for drivers that require host support (e.g. ath):
o remove IEEE80211_C_RCVMGT capability
o on transmit craft new nodes as needed using new ieee80211_find_txnode routine
o add ieee80211_find_txnode routine to lookup a node by mac address and
  if not present create one when operating in ibss/ahdemo mode; new nodes
  are dup'd from bss and the driver is told to treat the node as if a new
  association has been created so driver-private state (e.g. rate control
  handling) is setup

Obtained from:	netbsd (basic idea)
2004-04-02 23:25:39 +00:00
..
ieee80211_crypto.c add statistics for all failures and/or abnormal events; still need 2003-10-17 23:15:30 +00:00
ieee80211_crypto.h revise copyright notices per discussion with Atsushi Onoe <onoe@sm.sony.co.jp> 2003-06-27 05:13:52 +00:00
ieee80211_input.c always free node reference when processing a probe request frame; was 2004-04-02 23:12:45 +00:00
ieee80211_ioctl.c o add support for controlling the power of transmitted frames 2004-03-30 22:57:57 +00:00
ieee80211_ioctl.h o add support for controlling the power of transmitted frames 2004-03-30 22:57:57 +00:00
ieee80211_node.c fix adhoc/ibss operation for drivers that require host support (e.g. ath): 2004-04-02 23:25:39 +00:00
ieee80211_node.h fix adhoc/ibss operation for drivers that require host support (e.g. ath): 2004-04-02 23:25:39 +00:00
ieee80211_output.c fix adhoc/ibss operation for drivers that require host support (e.g. ath): 2004-04-02 23:25:39 +00:00
ieee80211_proto.c insure basic rate bit is set in derived rate set; this 2004-04-02 20:22:25 +00:00
ieee80211_proto.h MFp4 changes to fix locking issues and correct reference 2003-08-19 22:17:04 +00:00
ieee80211_radiotap.h Sync with netbsd: 2003-12-28 06:57:28 +00:00
ieee80211_var.h fix adhoc/ibss operation for drivers that require host support (e.g. ath): 2004-04-02 23:25:39 +00:00
ieee80211.c diff reduction against madwifi/p4 2004-04-02 20:19:20 +00:00
ieee80211.h Handle SIOCSIFMTU ioctl directly so we can apply 802.11-specific bounds. 2004-01-13 06:22:55 +00:00