wpa_supplicant package
Information on this package is covered here.
|
Package
|
Description
|
License
|
|
wpa_supplicant
|
Wireless Client supplicant
|
BSD, Devicescape Software, Inc.
|
(For information on modifying/extending this package, see the "Wireless Client Module (wpa_supplicant)" topic in the Developer Guide.)
Summary
WPA/IEEE 802.11i Features
The following IEEE 802.11i features are supported in the wpa_supplicant distributed with the Devicescape™ Universal Wireless Platform:
|
Security Modes, Features
|
Details
|
|
|
WPA-Personal
|
|
|
WPA-Enterprise (For example, with RADIUS authentication server.)
The following authentication methods are supported with an integrated IEEE: 802.1X Supplicant:
EAP-TLS
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)
EAP-TTLS/EAP-MD5-Challenge
EAP-TTLS/EAP-GTC
EAP-TTLS/EAP-OTP
EAP-TTLS/EAP-MSCHAPv2
EAP-TTLS/EAP-TLS
EAP-TTLS/MSCHAPv2
EAP-TTLS/MSCHAP
EAP-TTLS/PAP
EAP-TTLS/CHAP
EAP-SIM
EAP-AKA
EAP-PSK
LEAP (Requires special support from the driver for IEEE 802.11 authentication)
The following methods are supported, but since they do not generate keying material, they cannot be used with WPA or IEEE 802.1X WEP keying):
EAP-MD5-Challenge
EAP-MSCHAPv2
EAP-GTC
EAP-OTP
Alternatively, an external program, e.g., Xsupplicant, can be used for EAP authentication.
|
|
Key Management
|
Key management for CCMP, TKIP, WEP104, WEP40
|
|
|
- Pre-authentication
- PMKSA caching
|
Background on WPA and WPA2
Wi-Fi Protected Access (WPA)
The original security mechanism of IEEE 802.11 standard was not designed to be strong and has proven to be insufficient for most networks that require some kind of security. Task group I (Security) of IEEE 802.11 working group (http://www.ieee802.org/11/) has worked to address the flaws of the base standard as published in the IEEE 802.11i standard specification.
Wi-Fi Alliance (http://www.wi-fi.org/) used a draft version of the IEEE 802.11i work (draft 3.0) to define a subset of the security enhancements that can be implemented with existing wlan hardware. This is called Wi-Fi Protected Access (WPA). This has now become a mandatory component of interoperability testing and certification done by Wi-Fi Alliance. Wi-Fi provides information about WPA at its Web site
(http://www.wi-fi.org/OpenSection/protected_access.asp).
The IEEE 802.11 standard defined Wired Equivalent Privacy (WEP) algorithm for protecting wireless networks. WEP uses RC4 with 40-bit keys, 24-bit initialization vector (IV), and CRC32 to protect against packet forgery. All these choices have proven to be insufficient: key space is too small against current attacks, RC4 key scheduling is insufficient (beginning of the pseudorandom stream should be skipped), IV space is too small and IV reuse makes attacks easier, there is no replay protection, and non-keyed authentication does not protect against bitflipping packet data.
WPA is an intermediate solution for the security issues. It uses Temporal Key Integrity Protocol (TKIP) to replace WEP. TKIP is a compromise on strong security and possibility to use existing hardware. It still uses RC4 for the encryption like WEP, but with per-packet RC4 keys. In addition, it implements replay protection, keyed packet authentication mechanism (Michael MIC).
Keys can be managed using two different mechanisms. WPA can either use an external authentication server (for example, RADIUS) and EAP just like IEEE 802.1X is using or pre-shared keys without need for additional servers. Wi-Fi calls these WPA-Enterprise and WPA-Personal, respectively. Both mechanisms will generate a master session key for the Authenticator (AP) and Supplicant (client station).
WPA implements a new key handshake (4-Way Handshake and Group Key Handshake) for generating and exchanging data encryption keys between the Authenticator and Supplicant. This handshake is also used to verify that both Authenticator and Supplicant know the master session key. These handshakes are identical regardless of the selected key management mechanism (only the method for generating master session key changes).
IEEE 802.11i / WPA2
The design for parts of IEEE 802.11i that were not included in WPA has finished (May 2004) and this amendment to IEEE 802.11 was approved in June 2004. Wi-Fi Alliance is using the final IEEE 802.11i as a new version of WPA called WPA2. This includes, e.g., support for more robust encryption algorithm (CCMP: AES in Counter mode with CBC-MAC) to replace TKIP and optimizations for hand-off (reduced number of messages in initial key handshake, pre-authentication, and PMKSA caching).
Some wireless LAN vendors are already providing support for CCMP in their WPA products. There is no "official" interoperability certification for CCMP and/or mixed modes using both TKIP and CCMP, so some interoperability issues can be expected even though many combinations seem to be working with equipment from different vendors.Certification for WPA2 is likely to start during the second half of 2004.
Driver and Library Requirements
Drivers
wpa_supplicant is designed to be portable for different drivers and operating systems. Support for more WLAN cards and operating systems will be added in the future.
One main goal is to add full WPA/WPA2 support to Linux wireless extensions to allow new drivers to be supported without having to implement new driver-specific interface code in wpa_supplicant.
In theory, any driver that supports Linux wireless extensions can be used with IEEE 802.1X (that is, not WPA) when using ap_scan=0 option in configuration file.
In addition to the drivers officially supported by the platform (Atheros, Broadcom, and Conexant), you should also be able to use several other drivers with no source code modifications.
(See the wpa_supplicant topic in the Reference Design Guide for more information about the design of wpa_supplicant and on porting to other drivers.)
|
Driver
|
Description
|
|
Supported Drivers
|
|
Atheros driver
|
All drivers using Devicescape DataPath 80211.o are supported:
- Atheros driver for AR5212 and AR5213
- Atheros AR5312, AR2312, and AR2313 System-on-a-Chip (SoC) boards
(For information about the DataPath 80211.o driver, see ieee80211 package .)
|
|
Broadcom wl.o driver
|
Linux driver for Broadcom IEEE 802.11a/g cards
|
|
Conexant Prism GT/Duette/Indigo driver
|
Linux driver for Conexant cards using SoftMAC architecture
|
|
Unsupported Drivers (Not officially supported, but should not require porting to work)
|
|
Host AP driver for Prism2/2.5/3 (development snapshot/v0.2.x)
|
Development snapshot/v0.2.x is available at http://hostap.epitest.fi/
Driver must be set in Managed mode (iwconfig wlan0 mode managed)
The station firmware version needs to be 1.7.0 or newer to work in WPA mode.
|
|
Linuxant DriverLoader
|
Linuxant DriverLoader with Windows NDIS driver for your wlan card supporting WPA available at http://www.linuxant.com/driverloader/
|
|
Agere Systems Inc. Linux Driver
|
The driver interface file (driver_hermes.c) and hardware specific include files are not included in the wpa_supplicant distribution. You will need to copy these from the source package of the Agere driver.
|
|
Multiband Atheros Driver for WiFi (MADWIFI) driver for cards based on Atheros chip set (ar521x)
|
You will need to modify the wpa_supplicant .config file to use the correct path for the madwifi driver root directory (CFLAGS += -I../madwifi/wpa line in example defconfig).
|
|
ATMEL AT76C5XXx driver for USB and PCMCIA cards
|
|
|
Linux ndiswrapper
|
Linux ndiswrapper with Windows NDIS driver is available at http://ndiswrapper.sourceforge.net/
|
|
Intel ipw2100 driver
|
|
|
Intel ipw2200 driver
|
|
|
BSD net80211 layer
(For example, the Atheros driver)
|
For FreeBSD 6-CURRENT branch
|
Optional Libraries
Optional Libraries for Layer2 Packet Processing
- libpcap (tested with 0.7.2, most relatively recent versions assumed to work, this is likely to be available with most distributions, http://tcpdump.org/)
These libraries are not used in the default Linux build. Instead, internal Linux specific implementation is used. libpcap/libdnet are more portable and they can be used by adding CONFIG_DNET_PCAP=y into .config. They may also be selected automatically for other operating systems.
Optional Libraries for EAP-TLS, EAP-PEAP, and EAP-TTLS
openssl (tested with 0.9.7c and 0.9.7d, assumed to work with most relatively recent versions; this is likely to be available with most distributions, http://www.openssl.org/)
This library is only needed when EAP-TLS, EAP-PEAP, or EAP-TTLS support is enabled. WPA-PSK mode does not require this or EAPOL/EAP implementation. A configuration file, .config, for compilation is needed to enable IEEE 802.1X/EAPOL and EAP methods.
Note that EAP-MD5, EAP-GTC, EAP-OTP, and EAP-MSCHAPV2 cannot be used alone with WPA, so they should only be enabled if testing the EAPOL/EAP state machines. However, they can be used as inner authentication algorithms with EAP-PEAP and EAP-TTLS.
See Building and installing section below for more detailed information about the wpa_supplicant build time configuration.
Operational Description
wpa_supplicant is an implementation of the WPA Supplicant component; that is, 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 IEEE802.11 authentication/association of the WLAN 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 front-end programs and an example text-based front-end, wpa_cli, is included with wpa_supplicant.
The following steps are used when associating with an AP using WPA:
- wpa_supplicant requests the kernel driver to scan neighboring basic service sets (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 or external Xsupplicant 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
Usage
Start/Stop Options
Use the following commmands to control the the wpa_supplicant runtime service on the target device.
|
Action
|
Command
|
|
Start
|
/etc/init.d/wpa_supplicant start
|
|
Stop
|
/etc/init.d/wpa_supplicant stop
|
|
Restart
|
/etc/init.d/wpa_supplicant restart
|
The start and restart options will only start the wpa_supplicant daemon if the wireless client feature has been enabled in the /etc/default/wireless file (set the variable CLIENT to "yes" to enable wireless client mode). Both the ds-wireless-client and ds-wireless-client-bridge profile packages will enable wireless client functionality by default.
(See the Developer Guide topic on Creating Root File System Images for Reference Designs for information on building a reference client using the ds-wireless-client profile package.)
Configuration parameters set in the /etc/default/wpa_supplicant file and passed to the initialization script are:
|
Parameter
|
Description
|
|
DRIVER
|
Define the driver type the supplicant should use.
Supported options are:
- i802 - Atheros AR5K
- broadcom - Broadcom 430x and 4320
- islsoftmac - Conexant PrismGT and WorldRadio
|
|
INTERFACE
|
Define the wireless interface the supplicant should use. (For example wlan0 or eth2.)
|
Runtime Configuration (wpa_supplicant.conf)
wpa_supplicant.conf
wpa_supplicant is configured using a text file that lists all accepted networks and security policies, including pre-shared keys. See example configuration file, wpa_supplicant.conf, for detailed information about the configuration format and supported fields.
Changes to configuration file can be reloaded be sending SIGHUP signal to wpa_supplicant (killall -HUP wpa_supplicant). Similarly, reloading can be triggered with wpa_cli reconfigure command.
Configuration file can include one or more network blocks; for example, one for each used SSID. wpa_supplicant will automatically select the best betwork based on the order of network blocks in the configuration file, network security level (WPA/WPA2 is prefered), and signal strength.
The following section show example configuration files for some common configurations:
Example 1: WPA-Personal (PSK) Home and WPA-Enterprise with EAP-TLS Work Networks
This example configuration file sets up a WPA-Personal (PSK) as Home Network and WPA-Enterprise with EAP-TLS as a Work Network
# allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
#
# home network; allow all valid ciphers
network={
ssid="home"
scan_ssid=1
key_mgmt=WPA-PSK
psk="very secret passphrase"
}
#
# work network; use EAP-TLS with WPA; allow only CCMP and TKIP ciphers
network={
ssid="work"
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TLS
identity="user@example.com"
ca_cert="/etc/cert/ca.pem"
client_cert="/etc/cert/user.pem"
private_key="/etc/cert/user.prv"
private_key_passwd="password"
}
Example 2: WPA-RADIUS/EAP-PEAP/MSCHAPv2 with RADIUS (old peaplabel)
This example configuration file sets up WPA-RADIUS/EAP-PEAP/MSCHAPv2 with RADIUS servers that use the old peaplabel (for example, Funk Odyssey and SBR, Meetinghouse Aegis, Interlink RAD-Series).
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="example"
scan_ssid=1
key_mgmt=WPA-EAP
eap=PEAP
identity="user@example.com"
password="foobar"
ca_cert="/etc/cert/ca.pem"
phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
}
Example 3: EAP-TTLS/EAP-MD5-Challenge
This example configuration file sets up an EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the unencrypted use. The real identity is sent only within an encrypted TLS tunnel.
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="example"
scan_ssid=1
key_mgmt=WPA-EAP
eap=TTLS
identity="user@example.com"
anonymous_identity="anonymous@example.com"
password="foobar"
ca_cert="/etc/cert/ca.pem"
phase2="auth=MD5"
}
Example 4: IEEE 802.1X with Dynamic WEP Keys and EAP-TLS Authentication
This example configuration file sets up IEEE 802.1X (not WPA) with dynamic WEP keys (both unicast and broadcast required). EAP-TLS is used for authentication.
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="1x-test"
scan_ssid=1
key_mgmt=IEEE8021X
eap=TLS
identity="user@example.com"
ca_cert="/etc/cert/ca.pem"
client_cert="/etc/cert/user.pem"
private_key="/etc/cert/user.prv"
private_key_passwd="password"
eapol_flags=3
}
Example 5: Allow All Configuration Modes (for Testing Only)
The following is a "catch-all" example that allows (more or less) all configuration modes. The configuration options are used based on what security policy is used in the selected SSID. This is mostly for testing and is not recommended for normal use.
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="example"
scan_ssid=1
key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
pairwise=CCMP TKIP
group=CCMP TKIP WEP104 WEP40
psk="very secret passphrase"
eap=TTLS PEAP TLS
identity="user@example.com"
password="foobar"
ca_cert="/etc/cert/ca.pem"
client_cert="/etc/cert/user.pem"
private_key="/etc/cert/user.prv"
private_key_passwd="password"
phase1="peaplabel=0"
ca_cert2="/etc/cert/ca2.pem"
client_cert2="/etc/cer/user.pem"
private_key2="/etc/cer/user.prv"
private_key2_passwd="password"
}
Certificates
Some EAP authentication methods require use of certificates. EAP-TLS uses both server side and client certificates whereas EAP-PEAP and EAP-TTLS only require the server side certificate. When client certificate is used, a matching private key file has to also be included in configuration. If the private key uses a passphrase, this has to be configured in wpa_supplicant.conf (private_key_passwd).
Options that Must be Configured in the Drivers
Most options for client mode are set in wpa_supplicant.conf for all drivers. However, options for configuring the following features are not currently available in wpa_supplicant.conf and must be configured in the driver:
- Wi-Fi Multimedia Extensions (WMM)
- Wireless Monitor Mode (sniffer)
- Country/Regulatory Domain
Refer to the following driver topics for information on configuring these features in each driver:
Command Line Options
Syntax
wpa_supplicant [-BddehLqqvw] -i<ifname> -c<ConfigFile> [-D<driver>] \
[-N -i<ifname> -c<conf> [-D<driver>] ...]
Options
|
Option
|
Description
|
|
-B
|
Run daemon in the background
|
|
-K
|
Include keys (passwords, etc.) in debug output
|
|
-t
|
Include timestamp in debug messages
|
|
-e
|
Use external IEEE 802.1X Supplicant (e.g., xsupplicant) (this disables the internal Supplicant)
|
|
-h
|
Show this help text
|
|
-L
|
Show license (GPL and BSD)
|
|
-q
|
Decrease debugging verbosity (-qq even less)
|
|
-v
|
Show version
|
|
-w
|
Wait for interface to be added, if needed
|
|
-N
|
Start describing new interface drivers
|
Drivers
|
D<driver>
|
Description
|
|
hostap
|
Host AP driver (Intersil Prism2/2.5/3) . This is the default.
This can also be used with Linuxant DriverLoader
|
|
hermes
|
Agere Systems Inc. driver (Hermes-I/Hermes-II)
|
|
madwifi
|
MADWIFI 802.11 support (Atheros, for example)
|
|
atmel
|
ATMEL AT76C5XXx (USB, PCMCIA)
|
|
wext
|
Linux wireless extensions (generic)
|
|
ndiswrapper
|
Linux ndiswrapper
|
|
ndiswrapper
|
Linux ndiswrapper
|
|
broadcom
|
Broadcom wl.o driver
|
|
ipw
|
Intel ipw2100/2200 driver
|
|
bsd
|
BSD 802.11 support (Atheros, for example)
|
|
ndis
|
Windows NDIS driver
|
In most common cases, wpa_supplicant is started with the following options:
wpa_supplicant -Bw -c/etc/wpa_supplicant.conf -iwlan0
This makes the process fork into background and wait for the wlan0 interface if it is not available at startup time.
The easiest way to debug problems, and to get debug log for bug reports, is to start wpa_supplicant on foreground with debugging enabled:
wpa_supplicant -c/etc/wpa_supplicant.conf -iwlan0 -d
wpa_supplicant can control multiple interfaces (radios) either by running one process for each interface separately or by running just one process and list of options at the command line. Each interface is separated with -N argument. As an example, the following command would start wpa_supplicant for two interfaces:
wpa_supplicant \
-c wpa1.conf -i wlan0 -D hostap -N \
-c wpa2.conf -i ath0 -D madwifi
External APIs
wpa_cli
wpa_cli is a text-based front-end program for interacting with wpa_supplicant. It is used to query current status, change configuration, trigger events, and request interactive user input.
wpa_cli can show the current authentication status, selected security mode, dot11 and dot1x MIBs, etc. In addition, it can configuring some variables like EAPOL state machine parameters and trigger events like reassociation and IEEE 802.1X logoff/logon. wpa_cli provides a user interface to request authentication information, like username and password, if these are not included in the configuration. This can be used to implement; for example, one-time-passwords or generic token card authentication where the authentication is based on a challenge-response that uses an external device for generating the response.
The control interface of wpa_supplicant can be configured to allow non-root user access (ctrl_interface_group in the configuration file). This makes it possible to run wpa_cli with a normal user account.
wpa_cli supports two modes: interactive and command line. Both modes share the same command set and the main difference is in interactive mode providing access to unsolicited messages (event messages, username/password requests).
Interactive mode is started when wpa_cli is executed without including the command as a command line parameter. Commands are then entered on the wpa_cli prompt. In command line mode, the same commands are entered as command line arguments for wpa_cli.
Interactive Authentication Parameters Request
When wpa_supplicant need authentication parameters, like username and password, which are not present in the configuration file, it sends a request message to all attached front-end programs, for wpa_cli in interactive mode. wpa_cli shows these requests with "CTRL-REQ-<type>-<id>:<text>" prefix. <type> is IDENTITY, PASSWORD, or OTP (one-time-password). <id> is a unique identifier for the current network. <text> is description of the request. In case of OTP request, it includes the challenge from the authentication server.
The reply to these requests can be given with 'identity', 'password', and 'otp' commands. <id> needs to be copied from the the matching request. 'password' and 'otp' commands can be used regardless of whether the request was for PASSWORD or OTP. The main difference between these two commands is that values given with 'password' are remembered as long as wpa_supplicant is running whereas values given with 'otp' are used only once and then forgotten; that is, wpa_supplicant will ask front-end for a new value for every use. This can be used to implement one-time-password lists and generic token card -based authentication.
Example request for password and a matching reply:
CTRL-REQ-PASSWORD-1:Password needed for SSID foobar
> password 1 mysecretpassword
Example request for generic token card challenge-response:
CTRL-REQ-OTP-2:Challenge 1235663 needed for SSID foobar
> otp 2 9876
wpa_cli commands
status = get current WPA/EAPOL/EAP status
mib = get MIB variables (dot1x, dot11)
help = show this usage help
interface [ifname] = show interfaces/select interface
level <debug level> = change debug level
license = show full wpa_cli license
logoff = IEEE 802.1X EAPOL state machine logoff
logon = IEEE 802.1X EAPOL state machine logon
set = set variables (shows list of variables when run without arguments)
pmksa = show PMKSA cache
reassociate = force reassociation
reconfigure = force wpa_supplicant to re-read its configuration file
preauthenticate <BSSID> = force preauthentication
identity <network id> <identity> = configure identity for an SSID
password <network id> <password> = configure password for an SSID
otp <network id> <password> = configure one-time-password for an SSID
terminate = terminate wpa_supplicant
quit = exit wpa_cli
Building the Package
In order to be able to build wpa_supplicant, you will first need to select which parts of it will be included.
This is done by creating a build time configuration file, .config, in the wpa_supplicant root directory. Configuration options are text lines using following format: CONFIG_<option>=y. Lines starting with # are considered comments and are ignored. See defconfig file for example configuration and list of available option.
The build time configuration can be used to select only the needed features and limit the binary size and requirements for external libraries. The main configuration parts are the selection of which driver interfaces (for example, hostap, madwifi, and so on) and which authentication methods (e.g., EAP-TLS, EAP-PEAP, and so on) are included.
The following build time configuration options are used to control IEEE 802.1X/EAPOL and EAP state machines and all EAP methods. Including TLS, PEAP, or TTLS will require linking wpa_supplicant with openssl library for TLS implementation.
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_TLS=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_TTLS=y
CONFIG_EAP_GTC=y
CONFIG_EAP_OTP=y
CONFIG_EAP_SIM=y
CONFIG_EAP_AKA=y
CONFIG_EAP_PSK=y
CONFIG_EAP_LEAP=y
The following option can be used to include GSM SIM/USIM interface for GSM/UMTS authentication algorithm (for EAP-SIM/EAP-AKA). This requires pcsc-lite (http://www.linuxnet.com/) for smart card access.
CONFIG_PCSC=y
The following option can be used to replace the native Linux packet socket interface with libpcap/libdnet.
CONFIG_DNET_PCAP=y
The following options can be added to .config to select which driver interfaces are included. Prism54.org driver is not yet complete and Hermes driver interface needs to be downloaded from Agere (see above). Most Linux driver need to include CONFIG_WIRELESS_EXTENSION.
CONFIG_WIRELESS_EXTENSION=y
CONFIG_DRIVER_HOSTAP=y
CONFIG_DRIVER_PRISM54=y
CONFIG_DRIVER_HERMES=y
CONFIG_DRIVER_MADWIFI=y
CONFIG_DRIVER_ATMEL=y
CONFIG_DRIVER_WEXT=y
CONFIG_DRIVER_NDISWRAPPER=y
CONFIG_DRIVER_BROADCOM=y
CONFIG_DRIVER_IPW=y
CONFIG_DRIVER_BSD=y
CONFIG_DRIVER_NDIS=y
The following example includes all features and driver interfaces that are included in the wpa_supplicant package:
CONFIG_DRIVER_HOSTAP=y
CONFIG_DRIVER_PRISM54=y
CONFIG_DRIVER_HERMES=y
CONFIG_DRIVER_MADWIFI=y
CONFIG_DRIVER_ATMEL=y
CONFIG_DRIVER_WEXT=y
CONFIG_DRIVER_NDISWRAPPER=y
CONFIG_DRIVER_BROADCOM=y
CONFIG_DRIVER_IPW=y
CONFIG_DRIVER_BSD=y
CONFIG_DRIVER_NDIS=y
CONFIG_WIRELESS_EXTENSION=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_TLS=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_TTLS=y
CONFIG_EAP_GTC=y
CONFIG_EAP_OTP=y
CONFIG_EAP_SIM=y
CONFIG_EAP_AKA=y
CONFIG_EAP_PSK=y
CONFIG_EAP_LEAP=y
CONFIG_PCSC=y
EAP-PEAP and EAP-TTLS will automatically include configured EAP methods (MD5, OTP, GTC, MSCHAPV2) for inner authentication selection.
Licensing
BSD
Devicescape Software, Inc.
Related Packages
Required
One of the following:
Suggested
broadcom-wl package
client_bridge package
