Low Level API specification
cfg80211 driver for WLAN
cfg80211 is the Linux 802.11 configuration API. cfg80211 replaces Wireless-Extensions. nl80211 is used to configure a cfg80211 device and is used for kernel ←→ userspace communication. Wireless extensions is now in maintenance mode, no new features will be added to it, we'll only fix bugs for it. cfg80211 is now feature-par complete with wireless-extensions, it actually has a lot more features that are simply not available and will never be available through wireless extensions. When implementing a cfg80211 driver wireless extensions support is still provided automatically for you through cfg80211 through CONFIG_CFG80211_WEXT. Distributions no longer needing wireless extensions can remove this and are encouraged to do so. cfg80211 also provides full regulatory support, this is done through wireless-regdb and the usage of CRDA.
All new Linux wireless drivers should be written targeting either cfg80211 for fullmac devices or mac80211 for softmac devices.
Writing cfg80211 drivers
We now have a few cfg80211 drivers, a good example of a full cfg80211 drivers is the Atheros ath6kl driver. Instead of writing wext ioctls you now write cfg80211 operation callbacks and fill in the wiphy struct to indicate to cfg80211 its device capabilities.
Then you allocate the wiphy by specifying the cfg80211 ops and fill the wiphy. For more details refer to cfg80211.h and as an example driver you can read ath6kl (or any other cfg80211-only driver, or even mac80211.) There's a list of APIs per interface mode.
hostapd [-BdhKtv] config-file ...
The hostapd utility is an authenticator for IEEE 802.11 networks. It provides full support for WPA/IEEE 802.11i and can also act as an IEEE 802.1X Authenticator with a suitable backend Authentication Server (typi- cally FreeRADIUS). The hostapd utility implements the authentication protocols that piggyback on top of the normal IEEE 802.11 protocol mecha- nisms. To use hostapd as an authenticator, the underlying device must support some basic functionality such as the ability to set security information in the 802.11 management frames. Beware that not all devices have this support.
The hostapd utility is designed to be a ``daemon program that runs in the background and acts as the backend component controlling the wireless connection. It supports separate frontend programs such as the text- based frontend, hostapd_cli(8).
The following arguments must be specified on the command line:
- Use the settings in the specified configuration file; the name of
- the specified wireless interface is contained in this file. See
- hostapd.conf(5) for a description of the configuration file syn-
- Changes to the configuration file can be reloaded by sending a
- SIGHUP to the hostapd processor or with the hostapd_cli(8) utility,
- using ``hostapd_cli reconfigure.
The options are as follows:
-d Enable debugging messages. If this option is supplied twice, more verbose messages are displayed.
-h Show help text.
-t Include timestamps in debugging output.
-v Display version information on the terminal and exit.
-B Detach from the controlling terminal and run as a daemon process in the background.
-K Include key information in debugging output.
wpa_supplicant - Wi-Fi Protected Access client and IEEE 802.1X supplicant
wpa_supplicant [ -BddfhKLqqtuvW ] [ -iifname ] [ -cconfig file ] [ -Ddriver ] [ -PPID_file ] [ -foutput file ]
Wireless networks do not require physical access to the network equipment in the same way as wired networks. This makes it easier for unauthorized users to passively monitor a network and capture all transmitted frames. In addition, unauthorized use of the network is much easier. In many cases, this can happen even without user's explicit knowledge since the wireless LAN adapter may have been configured to automatically join any available network.
Link-layer encryption can be used to provide a layer of security for wireless networks. The original wireless LAN standard, IEEE 802.11, included a simple encryption mechanism, WEP. However, that proved to be flawed in many areas and network protected with WEP cannot be consider secure. IEEE 802.1X authentication and frequently changed dynamic WEP keys can be used to improve the network security, but even that has inherited security issues due to the use of WEP for encryption. Wi-Fi Protected Access and IEEE 802.11i amendment to the wireless LAN standard introduce a much improvement mechanism for securing wireless networks. IEEE 802.11i enabled networks that are using CCMP (encryption mechanism based on strong cryptographic algorithm AES) can finally be called secure used for applications which require efficient protection against unauthorized access.
wpa_supplicant is an implementation of the WPA Supplicant component, i.e., the part that runs in the client stations. It implements WPA key negotiation with a WPA Authenticator and EAP authentication with Authentication Server. In addition, it controls the roaming and IEEE 802.11 authentication/association of the wireless LAN driver.
wpa_supplicant is designed to be a "daemon" program that runs in the background and acts as the backend component controlling the wireless connection. wpa_supplicant supports separate frontend programs and an example text-based frontend, wpa_cli, is included with wpa_supplicant.
Before wpa_supplicant can do its work, the network interface must be available. That means that the physical device must be present and enabled, and the driver for the device must be loaded. The daemon will exit immediately if the device is not already available.
After wpa_supplicant has configured the network device, higher level configuration such as DHCP may proceed. There are a variety of ways to integrate wpa_supplicant into a machine's networking scripts, a few of which are described in sections below.
The following steps are used when associating with an AP using WPA:
- wpa_supplicant requests the kernel driver to scan neighboring BSSes
- wpa_supplicant selects a BSS based on its configuration
- wpa_supplicant requests the kernel driver to associate with the chosen BSS
- If WPA-EAP: integrated IEEE 802.1X Supplicant completes EAP authentication with the authentication server (proxied by the Authenticator in the AP)
- If WPA-EAP: master key is received from the IEEE 802.1X Supplicant
- If WPA-PSK: wpa_supplicant uses PSK as the master session key
- wpa_supplicant completes WPA 4-Way Handshake and Group Key Handshake with the Authenticator (AP)
- wpa_supplicant configures encryption keys for unicast and broadcast
- normal data packets can be transmitted and received
Supported WPA/IEEE 802.11i features:
- WPA-PSK ("WPA-Personal")
- WPA with EAP (e.g., with RADIUS authentication server) ("WPA-Enterprise") Following authentication methods are supported with an integrate IEEE 802.1X Supplicant:
- EAP-PEAP/MSCHAPv2 (both PEAPv0 and PEAPv1)
- EAP-PEAP/TLS (both PEAPv0 and PEAPv1)
- EAP-PEAP/GTC (both PEAPv0 and PEAPv1)
- EAP-PEAP/OTP (both PEAPv0 and PEAPv1)
- EAP-PEAP/MD5-Challenge (both PEAPv0 and PEAPv1)
- LEAP (note: requires special support from the driver for IEEE 802.11 authentication)
(following methods are supported, but since they do not generate keying material, they cannot be used with WPA or IEEE 802.1X WEP keying)
- key management for CCMP, TKIP, WEP104, WEP40
- RSN/WPA2 (IEEE 802.11i)
- PMKSA caching
A summary of available driver backends is below. Support for each of the driver backends is chosen at wpa_supplicant compile time. For a list of supported driver backends that may be used with the -D option on your system, refer to the help output of wpa_supplicant (wpa_supplicant -h).
- (default) Host AP driver (Intersil Prism2/2.5/3). (this can also be used with Linuxant DriverLoader).
- Agere Systems Inc. driver (Hermes-I/Hermes-II).
- MADWIFI 802.11 support (Atheros, etc.).
- ATMEL AT76C5XXx (USB, PCMCIA).
- Linux wireless extensions (generic).
- Linux ndiswrapper.
- Broadcom wl.o driver.
- Intel ipw2100/2200 driver.
- wpa_supplicant wired Ethernet driver
- wpa_supplicant Broadcom switch driver
- BSD 802.11 support (Atheros, etc.).
- Windows NDIS driver.
Command Line Options
Most command line options have global scope. Some are given per interface, and are only valid if at least one -i option is specified, otherwise they're ignored. Option groups for different interfaces must be separated by -N option.
- Optional bridge interface name. (Per interface)
- Run daemon in the background.
- Path to configuration file. (Per interface)
- Path to ctrl_interface socket (Per interface. Only used if -c is not).
- Interface to listen on. Multiple instances of this option can be present, one per interface, separated by -N option (see below).
- Increase debugging verbosity (-dd even more).
- Driver to use (can be multiple drivers: nl80211,wext). (Per interface, see the available options below.)
-f output file
- Log output to specified file instead of stdout.
-g global ctrl_interface
- Path to global ctrl_interface socket. If specified, interface definitions may be omitted.
- Include keys (passwords, etc.) in debug output.
- Include timestamp in debug messages.
- Help. Show a usage message.
- Show license (GPL and BSD).
- Driver parameters. (Per interface)
- Path to PID file.
- Decrease debugging verbosity (-q q even less).
- Enabled DBus control interface. If enabled, interface definitions may be omitted.
- Show version.
- Wait for a control interface monitor before starting.
- Start describing new interface.
iw support with WLAN management frames transmitted via nl80211
nl80211 is the new 802.11 netlink interface public header. Together with cfg80211 it is intended to replace Wireless-Extensions.
Please see the nl80211.h for details. You can find a Prpl hosted version here