|sta||A client station in an infrastructure bss (i.e. one that associates to an access point).|
|hostap||An access point in an infrastructure bss.|
|mesh||A mesh station in an MBSS network.|
|adhoc||A station in an IBSS network.|
|ahdemo||A station operating in adhoc demo mode. This is essentially an IBSS station that does not use management frames (e.g. no beacons are transmitted). An ahdemo interface is especially useful for applications that want to transmit and receive raw 802.11 packets.|
|An interface used exclusively for capturing 802.11 frames. In particular this specified to have read-only properties which enables it to be operated on frequencies where one would otherwise not be allowed.|
|wds||A station that passes 4-address 802.11 traffic for the purpose of tunneling traffic over a wireless link. Typically this station would share the same MAC address as a hostap interface. It may be possible to create wds interfaces without a companion hostap interface but that is not guaranteed; one may need to create a hostap interface that does not send beacon frames before wds interfaces may be created.|
Note that an interfaces type cannot be changed once it is created.
wlan defines several mechanisms by which plugin modules may be used to extend its functionality. Cryptographic support such as WEP, TKIP, and AES-CCMP are implemented as standalone modules (if not statically configured into a system) that register with wlan. Similarly there is an authenticator framework for defining 802.11 authentication services and a framework for integrating access control mechanisms specific to the 802.11 protocol.
If the IEEE80211_DEBUG option is included in the kernel configuration, debugging controls are available using:
where X is the number of the wlan instance and mask is a bit-or of control bits that determine which debugging messages to enable. For example,
enables debugging messages related to scanning for an access point, adhoc neighbor, or an unoccupied channel when operation as an access point. The wlandebug(8) tool provides a more user-friendly mechanism for doing the same thing. Note that
defines the initial value of the debugging flags for each cloned wlan interface; this is useful to enable debug messages during interface creation.
The module name of wlan was used to be compatible with
Mesh stations follow the 802.11s Draft 3.0 specification which is not ratified and subject to change. Beware that this specification is incompatible with earlier drafts; and stations implementing earlier drafts (e.g. Linux) may not interoperate.
an(4), ath(4), bwi(4), bwn(4), ipw(4), iwi(4), iwn(4), malo(4), mwl(4), netintro(4), ral(4), rsu(4), rum(4), run(4), uath(4), upgt(4), ural(4), urtw(4), urtwn(4), wi(4), wlan_acl(4), wlan_ccmp(4), wlan_tkip(4), wlan_wep(4), wlan_xauth(4), wpi(4), zyd(4)
More information can be found in the IEEE 802.11 Standards.
The wlan driver first appeared in
.Fx 5.0 .
Atsushi Onoe is the author of original
.Nx software from which this work began.
.An Sam Leffler brought the code into
.Fx and then rewrote it to support multi-mode devices, 802.11g, 802.11n, WPA/802.11i, WME, multi-bss, and add the extensible frameworks for cryptographic, authentication, and access control plugins. This manual page was written by
.An Tom Rhodes Aq trhodes@FreeBSD.org .