summaryrefslogtreecommitdiffstats
path: root/sys/net80211
Commit message (Collapse)AuthorAgeFilesLines
* enable "aggressive mode" only when operating in ap or station mode; insam2006-01-021-1/+1
| | | | | | | | particular this fixes use of wme in adhoc demo mode, it wasn't possible to set the txop limit because the aggressive mode logic would override Reviewed by: apatti MFC after: 2 weeks
* update erp information element in the beacon frame to reflectsam2006-01-024-4/+21
| | | | | | | | changes in the bss Reviewed by: avatar Obtained from: atheros MFC after: 2 weeks
* correct checking for turbo channels: rev 1.24 fixed static turbo channelssam2005-12-301-4/+4
| | | | | | | | but broke handling of the turboG channel; since we aren't ready to revamp the channel list just check for turboA channels for now so channel 6 is considered in auto mode Noticed by: gibbs
* correct (reversed) ms<->tu macrossam2005-12-291-2/+2
| | | | Reviewed by: apatti, kcyu
* - Fix VLAN_INPUT_TAG() macro, so that it doesn't touch mtag inglebius2005-12-181-2/+3
| | | | | | | | | case if memory allocation failed. - Remove fourth argument from VLAN_INPUT_TAG(), that was used incorrectly in almost all drivers. Indicate failure with mbuf value of NULL. In collaboration with: yongari, ru, sam
* make packet bursting configurable (default to on if device is capable)sam2005-12-145-1/+17
|
* When creating neighbor entries for an ahdemo bss apply the localsam2005-12-141-0/+9
| | | | | settings. In particular this allows us to use QoS frames in a bss and in turn enables disabling ack's.
* when creating an ahdemo bss use any requested bssid; otherwise use zerosam2005-12-141-0/+5
| | | | Obtained from: madwifi
* allow setting the bssid in any modesam2005-12-141-3/+0
| | | | Obtained from: netbsd
* disallow module unload when there are dynamic referencessam2005-12-123-3/+42
| | | | MFC after: 1 week
* propagate current bss state on sta join so, in particular, authmodesam2005-12-121-2/+4
| | | | | | is set properly in the new bss node MFC after: 2 weeks
* Bandaid ieee80211_set_chan to handle a channel parameter of "any";sam2005-12-121-1/+3
| | | | | | | | | this can happen under certain conditions when scanning. This logic will eventually go away with the new scanning code. While here de-inline the routine. MFC after: 1 week
* o correct auto mode logic for avoiding turbo channelssam2005-12-121-9/+9
| | | | | | | o correct assumption that a static turbo channel is also usable in 11a; the opposite is true MFC after: 1 week
* Add ieee80211_beacon_miss for processing sta mode beacon miss eventssam2005-12-125-0/+47
| | | | | | | in the 802.11 layer: we send a directed probe request frame to the current ap bmiss_max times (w/o answer) before scanning for a new ap. MFC after: 2 weeks
* add some useful definitions that'll be used soonsam2005-12-121-0/+6
|
* add fixed rate for sending multicast framessam2005-12-124-0/+10
| | | | | Obtained from: atheros MFC after: 1 week
* change malloc when setting an optional ie to use M_NOWAITsam2005-12-121-2/+1
| | | | MFC after: 3 days
* correct parameter check when retrieving the current channel listsam2005-12-121-1/+1
| | | | MFC after: 3 days
* correct handling of dtim for periods > 1sam2005-12-051-1/+1
| | | | Obtained from: madwifi
* Adhoc mode fixups:sam2005-12-043-28/+56
| | | | | | | | | | | | | | o plug memory leak in adhoc mode: on rx the sender may be the current master so simply checking against ic_bss is not enough to identify if the packet comes from an unknown sender; must also check the mac address o split neighbor node creation into two routines and fillin state of nodes faked up on xmit when a beacon or probe response frame is later received; this ensures important state like the rate set and advertised capabilities are correct Obtained from: netbsd MFC after: 1 week
* fix dynamic changes in short slottime for 11g sta mode: set thesam2005-11-301-1/+1
| | | | | | | slot time based on the rcvd capabilities, not the existing ones Obtained from: atheros MFC after: 1 week
* Update ieee80211_mhz2ieee to understand public safety bands and spectrumsam2005-11-152-9/+24
| | | | | | | that can potentially be mapped to negative ieee #'s. NB: before operation on the latter can be supported we need to cleanup various code that assumes ieee channel #'s are >= 0
* - Store pointer to the link-level address right in "struct ifnet"ru2005-11-111-3/+3
| | | | | | | | | | rather than in ifindex_table[]; all (except one) accesses are through ifp anyway. IF_LLADDR() works faster, and all (except one) ifaddr_byindex() users were converted to use ifp->if_addr. - Stop storing a (pointer to) Ethernet address in "struct arpcom", and drop the IFP2ENADDR() macro; all users have been converted to use IF_LLADDR() instead.
* Retire MT_HEADER mbuf type and change its users to use MT_DATA.andre2005-11-022-3/+3
| | | | | | | | | | | | Having an additional MT_HEADER mbuf type is superfluous and redundant as nothing depends on it. It only adds a layer of confusion. The distinction between header mbuf's and data mbuf's is solely done through the m->m_flags M_PKTHDR flag. Non-native code is not changed in this commit. For compatibility MT_HEADER is mapped to MT_DATA. Sponsored by: TCP/IP Optimization Fundraise 2005
* Properly set ic_curchan before calling back to device driver to do channelavatar2005-08-301-2/+12
| | | | | | | | switching(ifconfig devX channel Y). This fix should make channel changing works again in monitor mode. Submitted by: sam X-MFC-With: other ic_curchan changes
* revert 1.64: we cannot use the channel characteristics to decide when tosam2005-08-131-4/+3
| | | | | | | do 11g erp sta accounting because b/g channels show up as false positives when operating in 11b. Noticed by: Michal Mertl
* Extend acl support to pass ioctl requests through and use this tosam2005-08-134-4/+79
| | | | | | | | add support for getting the current policy setting and collecting the list of mac addresses in the acl table. Submitted by: Michal Mertl (original version) MFC after: 2 weeks
* Don't use ic_curmode to decide when to do 11g station accounting,sam2005-08-102-5/+6
| | | | | | | | | | use the station channel properties. Fixes assert failure/bogus operation when an ap is operating in 11a and has associated stations then switches to 11g. Noticed by: Michal Mertl Reviewed by: avatar MFC after: 2 weeks
* Clarify/fix handling of the current channel:sam2005-08-109-220/+316
| | | | | | | | | | | | | | | | | | | o add ic_curchan and use it uniformly for specifying the current channel instead of overloading ic->ic_bss->ni_chan (or in some drivers ic_ibss_chan) o add ieee80211_scanparams structure to encapsulate scanning-related state captured for rx frames o move rx beacon+probe response frame handling into separate routines o change beacon+probe response handling to treat the scan table more like a scan cache--look for an existing entry before adding a new one; this combined with ic_curchan use corrects handling of stations that were previously found at a different channel o move adhoc neighbor discovery by beacon+probe response frames to a new ieee80211_add_neighbor routine Reviewed by: avatar Tested by: avatar, Michal Mertl MFC after: 2 weeks
* Propagate rename of IFF_OACTIVE and IFF_RUNNING to IFF_DRV_OACTIVE andrwatson2005-08-091-1/+2
| | | | | | | | | | | | | | IFF_DRV_RUNNING, as well as the move from ifnet.if_flags to ifnet.if_drv_flags. Device drivers are now responsible for synchronizing access to these flags, as they are in if_drv_flags. This helps prevent races between the network stack and device driver in maintaining the interface flags field. Many __FreeBSD__ and __FreeBSD_version checks maintained and continued; some less so. Reviewed by: pjd, bz MFC after: 7 days
* Split crypto tx+rx key indices and add a key index -> node mapping table:sam2005-08-088-76/+280
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Crypto changes: o change driver/net80211 key_alloc api to return tx+rx key indices; a driver can leave the rx key index set to IEEE80211_KEYIX_NONE or set it to be the same as the tx key index (the former disables use of the key index in building the keyix->node mapping table and is the default setup for naive drivers by null_key_alloc) o add cs_max_keyid to crypto state to specify the max h/w key index a driver will return; this is used to allocate the key index mapping table and to bounds check table loookups o while here introduce ieee80211_keyix (finally) for the type of a h/w key index o change crypto notifiers for rx failures to pass the rx key index up as appropriate (michael failure, replay, etc.) Node table changes: o optionally allocate a h/w key index to node mapping table for the station table using the max key index setting supplied by drivers (note the scan table does not get a map) o defer node table allocation to lateattach so the driver has a chance to set the max key id to size the key index map o while here also defer the aid bitmap allocation o add new ieee80211_find_rxnode_withkey api to find a sta/node entry on frame receive with an optional h/w key index to use in checking mapping table; also updates the map if it does a hash lookup and the found node has a rx key index set in the unicast key; note this work is separated from the old ieee80211_find_rxnode call so drivers do not need to be aware of the new mechanism o move some node table manipulation under the node table lock to close a race on node delete o add ieee80211_node_delucastkey to do the dirty work of deleting unicast key state for a node (deletes any key and handles key map references) Ath driver: o nuke private sc_keyixmap mechansim in favor of net80211 support o update key alloc api These changes close several race conditions for the ath driver operating in ap mode. Other drivers should see no change. Station mode operation for ath no longer uses the key index map but performance tests show no noticeable change and this will be fixed when the scan table is eliminated with the new scanning support. Tested by: Michal Mertl, avatar, others Reviewed by: avatar, others MFC after: 2 weeks
* use ieee80211_iterate_nodes to retrieve station data; the previoussam2005-08-081-45/+89
| | | | | | code walked the list w/o locking MFC after: 1 week
* Cleanup beacon/listen interval handling:sam2005-08-087-14/+29
| | | | | | | | | | | | | | | | | o separate configured beacon interval from listen interval; this avoids potential use of one value for the other (e.g. setting powersavesleep to 0 clobbers the beacon interval used in hostap or ibss mode) o bounds check the beacon interval received in probe response and beacon frames and drop frames with bogus settings; not clear if we should instead clamp the value as any alteration would result in mismatched sta+ap configuration and probably be more confusing (don't want to log to the console but perhaps ok with rate limiting) o while here up max beacon interval to reflect WiFi standard Noticed by: Martin <nakal@nurfuerspam.de> MFC after: 1 week
* fix debug msg typosam2005-08-061-1/+1
| | | | MFC after: 3 days
* Fix handling of frames sent prior to a station being authorizedsam2005-08-063-2/+40
| | | | | | | | | | | | when operating in ap mode. Previously we allocated a node from the station table, sent the frame (using the node), then released the reference that "held the frame in the table". But while the frame was in flight the node might be reclaimed which could lead to problems. The solution is to add an ieee80211_tmp_node routine that crafts a node that does exist in a table and so isn't ever reclaimed; it exists only so long as the associated frame is in flight. MFC after: 5 days
* close a race between reclaiming a node when a station is inactivesam2005-07-313-2/+15
| | | | | | and sending the null data frame used to probe inactive stations MFC after: 5 days
* when bridging internally bypass the bss node as traffic to itsam2005-07-271-11/+21
| | | | | | | must follow the normal input path Submitted by: Michal Mertl MFC after: 5 days
* bandaid ni_fails handling so ap's with association failures aresam2005-07-271-18/+24
| | | | | | | | reconsidered after a bit; a proper fix involves more changes to the scanning infrastructure Reviewed by: avatar, David Young MFC after: 5 days
* the AREF flag is only meaningful in ap mode; adhoc neighbors nowsam2005-07-231-1/+2
| | | | are timed out of the sta/neighbor table
* o move inactivity-related debug msgs under IEEE80211_MSG_INACTsam2005-07-221-8/+12
| | | | | | | o probe inactive neighbors in adhoc mode (they don't have an association id so previously were being timed out) MFC after: 3 days
* split xmit of probe request frame out into a separate routine thatsam2005-07-224-50/+96
| | | | | | | takes explicit parameters; this will be needed when scanning is decoupled from the state machine to do bg scanning MFC after: 3 days
* split 802.11 frame xmit setup code into ieee80211_send_setupsam2005-07-221-36/+72
| | | | MFC after: 3 days
* simplify ic_newassoc callbacksam2005-07-222-4/+3
| | | | MFC after: 3 days
* simplify ieee80211_ibss_merge apisam2005-07-222-2/+3
| | | | MFC after: 3 days
* add stats we know we'll need soon and some spare fields for future expansionsam2005-07-221-0/+8
| | | | MFC after: 3 days
* simplify tim callback apisam2005-07-224-12/+11
| | | | MFC after: 3 days
* don't include 802.3 header in min frame length calculation as it maysam2005-07-221-1/+1
| | | | | | | | not be present for a frag; fixes problem with small (fragmented) frames being dropped Obtained from: Atheros MFC after: 3 days
* simplify ieee80211_node_authorize and ieee80211_node_unauthorize api'ssam2005-07-226-13/+13
| | | | MFC after: 3 days
* simplifiy ieee80211_send_nulldata apisam2005-07-224-4/+5
| | | | MFC after: 3 days
* simplify rate set api's by removing ic parameter (implicit in node reference)sam2005-07-224-13/+16
| | | | MFC after: 3 days
OpenPOWER on IntegriCloud