596 lines
17 KiB
HTML
596 lines
17 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML><HEAD><TITLE>Man page of WPA_SUPPLICANT</TITLE>
|
|
</HEAD><BODY>
|
|
<H1>WPA_SUPPLICANT</H1>
|
|
Section: (8)<BR>Updated: 01 March 2021<BR><A HREF="#index">Index</A>
|
|
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
|
|
|
<P>
|
|
<A NAME="lbAB"> </A>
|
|
<H2>NAME</H2>
|
|
|
|
wpa_supplicant - Wi-Fi Protected Access client and IEEE 802.1X supplicant
|
|
<A NAME="lbAC"> </A>
|
|
<H2>SYNOPSIS</H2>
|
|
|
|
<P>
|
|
<B>wpa_supplicant</B> [ <B>-BddfhKLqqsTtuvW</B> ] [ <B>-i</B><I>ifname</I><B></B> ] [ <B>-c</B><I>config file</I><B></B> ] [ <B>-D</B><I>driver</I><B></B> ] [ <B>-P</B><I>PID_file</I><B></B> ] [ <B>-f</B><I>output file</I><B></B> ]
|
|
<P>
|
|
<A NAME="lbAD"> </A>
|
|
<H2>OVERVIEW</H2>
|
|
|
|
<P>
|
|
|
|
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.
|
|
<P>
|
|
|
|
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.
|
|
<P>
|
|
|
|
<B>wpa_supplicant</B> 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.
|
|
<P>
|
|
|
|
<B>wpa_supplicant</B> is designed to be a
|
|
"daemon" program that runs in the background and acts as the
|
|
backend component controlling the wireless
|
|
connection. <B>wpa_supplicant</B> supports separate
|
|
frontend programs and an example text-based frontend,
|
|
<B>wpa_cli</B>, is included with
|
|
wpa_supplicant.
|
|
<P>
|
|
|
|
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.
|
|
<P>
|
|
|
|
After <B>wpa_supplicant</B> 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.
|
|
<P>
|
|
|
|
The following steps are used when associating with an AP
|
|
using WPA:
|
|
<DL COMPACT>
|
|
<DT id="1">•<DD>
|
|
<B>wpa_supplicant</B> requests the kernel
|
|
driver to scan neighboring BSSes
|
|
<DT id="2">•<DD>
|
|
<B>wpa_supplicant</B> selects a BSS based on
|
|
its configuration
|
|
<DT id="3">•<DD>
|
|
<B>wpa_supplicant</B> requests the kernel
|
|
driver to associate with the chosen BSS
|
|
<DT id="4">•<DD>
|
|
If WPA-EAP: integrated IEEE 802.1X Supplicant
|
|
completes EAP authentication with the
|
|
authentication server (proxied by the Authenticator in the
|
|
AP)
|
|
<DT id="5">•<DD>
|
|
If WPA-EAP: master key is received from the IEEE 802.1X
|
|
Supplicant
|
|
<DT id="6">•<DD>
|
|
If WPA-PSK: <B>wpa_supplicant</B> uses PSK
|
|
as the master session key
|
|
<DT id="7">•<DD>
|
|
<B>wpa_supplicant</B> completes WPA 4-Way
|
|
Handshake and Group Key Handshake with the Authenticator
|
|
(AP)
|
|
<DT id="8">•<DD>
|
|
<B>wpa_supplicant</B> configures encryption
|
|
keys for unicast and broadcast
|
|
<DT id="9">•<DD>
|
|
normal data packets can be transmitted and received
|
|
</DL>
|
|
<A NAME="lbAE"> </A>
|
|
<H2>SUPPORTED FEATURES</H2>
|
|
|
|
<P>
|
|
|
|
Supported WPA/IEEE 802.11i features:
|
|
<DL COMPACT>
|
|
<DT id="10">•<DD>
|
|
WPA-PSK ("WPA-Personal")
|
|
<DT id="11">•<DD>
|
|
WPA with EAP (e.g., with RADIUS authentication server)
|
|
("WPA-Enterprise") Following authentication methods are
|
|
supported with an integrate IEEE 802.1X Supplicant:
|
|
<DL COMPACT><DT id="12"><DD>
|
|
<DL COMPACT>
|
|
<DT id="13">•<DD>
|
|
EAP-TLS
|
|
</DL>
|
|
</DL>
|
|
|
|
<DL COMPACT><DT id="14"><DD>
|
|
<DL COMPACT>
|
|
<DT id="15">•<DD>
|
|
EAP-PEAP/MSCHAPv2 (both PEAPv0 and PEAPv1)
|
|
<DT id="16">•<DD>
|
|
EAP-PEAP/TLS (both PEAPv0 and PEAPv1)
|
|
<DT id="17">•<DD>
|
|
EAP-PEAP/GTC (both PEAPv0 and PEAPv1)
|
|
<DT id="18">•<DD>
|
|
EAP-PEAP/OTP (both PEAPv0 and PEAPv1)
|
|
<DT id="19">•<DD>
|
|
EAP-PEAP/MD5-Challenge (both PEAPv0 and PEAPv1)
|
|
<DT id="20">•<DD>
|
|
EAP-TTLS/EAP-MD5-Challenge
|
|
<DT id="21">•<DD>
|
|
EAP-TTLS/EAP-GTC
|
|
<DT id="22">•<DD>
|
|
EAP-TTLS/EAP-OTP
|
|
<DT id="23">•<DD>
|
|
EAP-TTLS/EAP-MSCHAPv2
|
|
<DT id="24">•<DD>
|
|
EAP-TTLS/EAP-TLS
|
|
<DT id="25">•<DD>
|
|
EAP-TTLS/MSCHAPv2
|
|
<DT id="26">•<DD>
|
|
EAP-TTLS/MSCHAP
|
|
<DT id="27">•<DD>
|
|
EAP-TTLS/PAP
|
|
<DT id="28">•<DD>
|
|
EAP-TTLS/CHAP
|
|
<DT id="29">•<DD>
|
|
EAP-SIM
|
|
<DT id="30">•<DD>
|
|
EAP-AKA
|
|
<DT id="31">•<DD>
|
|
EAP-PSK
|
|
<DT id="32">•<DD>
|
|
EAP-PAX
|
|
<DT id="33">•<DD>
|
|
LEAP (note: requires special support from
|
|
the driver for IEEE 802.11 authentication)
|
|
<DT id="34">•<DD>
|
|
(following methods are supported, but since
|
|
they do not generate keying material, they cannot be used
|
|
with WPA or IEEE 802.1X WEP keying)
|
|
<DT id="35">•<DD>
|
|
EAP-MD5-Challenge
|
|
<DT id="36">•<DD>
|
|
EAP-MSCHAPv2
|
|
<DT id="37">•<DD>
|
|
EAP-GTC
|
|
<DT id="38">•<DD>
|
|
EAP-OTP
|
|
</DL>
|
|
</DL>
|
|
|
|
<DT id="39">•<DD>
|
|
key management for CCMP, TKIP, WEP104, WEP40
|
|
<DT id="40">•<DD>
|
|
RSN/WPA2 (IEEE 802.11i)
|
|
<DL COMPACT><DT id="41"><DD>
|
|
<DL COMPACT>
|
|
<DT id="42">•<DD>
|
|
pre-authentication
|
|
<DT id="43">•<DD>
|
|
PMKSA caching
|
|
</DL>
|
|
</DL>
|
|
|
|
</DL>
|
|
<A NAME="lbAF"> </A>
|
|
<H2>AVAILABLE DRIVERS</H2>
|
|
|
|
<P>
|
|
|
|
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
|
|
(<B>wpa_supplicant -h</B>).
|
|
<DL COMPACT>
|
|
<DT id="44"><B>nl80211</B><DD>
|
|
Uses the modern Linux nl80211/cfg80211 netlink-based
|
|
interface (most new drivers).
|
|
<DT id="45"><B>wext</B><DD>
|
|
Uses the legacy Linux wireless extensions ioctl-based
|
|
interface (older hardware/drivers).
|
|
<DT id="46"><B>wired</B><DD>
|
|
wpa_supplicant wired Ethernet driver
|
|
<DT id="47"><B>roboswitch</B><DD>
|
|
wpa_supplicant Broadcom switch driver
|
|
<DT id="48"><B>bsd</B><DD>
|
|
BSD 802.11 support (Atheros, etc.).
|
|
<DT id="49"><B>ndis</B><DD>
|
|
Windows NDIS driver.
|
|
</DL>
|
|
<A NAME="lbAG"> </A>
|
|
<H2>COMMAND LINE OPTIONS</H2>
|
|
|
|
<P>
|
|
|
|
Most command line options have global scope. Some are given per
|
|
interface, and are only valid if at least one <B>-i</B> option
|
|
is specified, otherwise they're ignored. Option groups for different
|
|
interfaces must be separated by <B>-N</B> option.
|
|
<DL COMPACT>
|
|
<DT id="50"><B>-b br_ifname</B><DD>
|
|
Optional bridge interface name. (Per interface)
|
|
<DT id="51"><B>-B</B><DD>
|
|
Run daemon in the background.
|
|
<DT id="52"><B>-c filename</B><DD>
|
|
Path to configuration file. (Per interface)
|
|
<DT id="53"><B>-C ctrl_interface</B><DD>
|
|
Path to ctrl_interface socket (Per interface. Only used if
|
|
<B>-c</B> is not).
|
|
<DT id="54"><B>-i ifname</B><DD>
|
|
Interface to listen on. Multiple instances of this option can
|
|
be present, one per interface, separated by <B>-N</B>
|
|
option (see below).
|
|
<DT id="55"><B>-d</B><DD>
|
|
Increase debugging verbosity (<B>-dd</B> even
|
|
more).
|
|
<DT id="56"><B>-D driver</B><DD>
|
|
Driver to use (can be multiple drivers: nl80211,wext).
|
|
(Per interface, see the available options below.)
|
|
<DT id="57"><B>-e entropy file</B><DD>
|
|
File for <B>wpa_supplicant</B> to use to
|
|
maintain its internal entropy store in over restarts.
|
|
<DT id="58"><B>-f output file</B><DD>
|
|
Log output to specified file instead of stdout. (This
|
|
is only available if <B>wpa_supplicant</B> was
|
|
built with the CONFIG_DEBUG_FILE
|
|
option.)
|
|
<DT id="59"><B>-g global ctrl_interface</B><DD>
|
|
Path to global ctrl_interface socket. If specified, interface
|
|
definitions may be omitted.
|
|
<DT id="60"><B>-K</B><DD>
|
|
Include keys (passwords, etc.) in debug output.
|
|
<DT id="61"><B>-h</B><DD>
|
|
Help. Show a usage message.
|
|
<DT id="62"><B>-L</B><DD>
|
|
Show license (BSD).
|
|
<DT id="63"><B>-o override driver</B><DD>
|
|
Override the driver parameter for new
|
|
interfaces.
|
|
<DT id="64"><B>-O override ctrl_interface</B><DD>
|
|
Override the ctrl_interface parameter for new
|
|
interfaces.
|
|
<DT id="65"><B>-p</B><DD>
|
|
Driver parameters. (Per interface)
|
|
<DT id="66"><B>-P PID_file</B><DD>
|
|
Path to PID file.
|
|
<DT id="67"><B>-q</B><DD>
|
|
Decrease debugging verbosity (<B>-qq</B> even
|
|
less).
|
|
<DT id="68"><B>-s</B><DD>
|
|
Log output to syslog instead of stdout. (This is only
|
|
available if <B>wpa_supplicant</B> was built
|
|
with the CONFIG_DEBUG_SYSLOG
|
|
option.)
|
|
<DT id="69"><B>-T</B><DD>
|
|
Log output to Linux tracing in addition to any other
|
|
destinations. (This is only available
|
|
if <B>wpa_supplicant</B> was built with
|
|
the CONFIG_DEBUG_LINUX_TRACING
|
|
option.)
|
|
<DT id="70"><B>-t</B><DD>
|
|
Include timestamp in debug messages.
|
|
<DT id="71"><B>-u</B><DD>
|
|
Enable DBus control interface. If enabled, interface
|
|
definitions may be omitted. (This is only available
|
|
if <B>wpa_supplicant</B> was built with
|
|
the CONFIG_CTRL_IFACE_DBUS_NEW option.)
|
|
<DT id="72"><B>-v</B><DD>
|
|
Show version.
|
|
<DT id="73"><B>-W</B><DD>
|
|
Wait for a control interface monitor before starting.
|
|
<DT id="74"><B>-N</B><DD>
|
|
Start describing new interface.
|
|
</DL>
|
|
<A NAME="lbAH"> </A>
|
|
<H2>EXAMPLES</H2>
|
|
|
|
<P>
|
|
|
|
In most common cases, <B>wpa_supplicant</B> is
|
|
started with:
|
|
<P>
|
|
<DL COMPACT><DT id="75"><DD>
|
|
<P>
|
|
<PRE>
|
|
wpa_supplicant -B -c/etc/wpa_supplicant.conf -iwlan0
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
|
|
This makes the process fork into background.
|
|
<P>
|
|
|
|
The easiest way to debug problems, and to get debug log for
|
|
bug reports, is to start <B>wpa_supplicant</B> on
|
|
foreground with debugging enabled:
|
|
<P>
|
|
<DL COMPACT><DT id="76"><DD>
|
|
<P>
|
|
<PRE>
|
|
wpa_supplicant -c/etc/wpa_supplicant.conf -iwlan0 -d
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
|
|
If the specific driver wrapper is not known beforehand, it is
|
|
possible to specify multiple comma separated driver wrappers on the command
|
|
line. <B>wpa_supplicant</B> will use the first driver
|
|
wrapper that is able to initialize the interface.
|
|
<P>
|
|
<DL COMPACT><DT id="77"><DD>
|
|
<P>
|
|
<PRE>
|
|
wpa_supplicant -Dnl80211,wext -c/etc/wpa_supplicant.conf -iwlan0
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
|
|
<B>wpa_supplicant</B> 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 command line. Each interface is separated with -N
|
|
argument. As an example, following command would start
|
|
wpa_supplicant for two interfaces:
|
|
<P>
|
|
<DL COMPACT><DT id="78"><DD>
|
|
<P>
|
|
<PRE>
|
|
wpa_supplicant \
|
|
-c wpa1.conf -i wlan0 -D nl80211 -N \
|
|
-c wpa2.conf -i ath0 -D wext
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<A NAME="lbAI"> </A>
|
|
<H2>OS REQUIREMENTS</H2>
|
|
|
|
<P>
|
|
|
|
Current hardware/software requirements:
|
|
<DL COMPACT>
|
|
<DT id="79">•<DD>
|
|
Linux kernel 2.6.30 or higher with
|
|
nl80211/cfg80211 support
|
|
<DT id="80">•<DD>
|
|
Linux kernel 2.4.x or higher with Linux Wireless
|
|
Extensions v15 or newer
|
|
<DT id="81">•<DD>
|
|
FreeBSD 6-CURRENT
|
|
<DT id="82">•<DD>
|
|
Microsoft Windows with WinPcap (at least WinXP, may work
|
|
with other versions)
|
|
</DL>
|
|
<A NAME="lbAJ"> </A>
|
|
<H2>SUPPORTED DRIVERS</H2>
|
|
|
|
<DL COMPACT>
|
|
<DT id="83"><B>Linux nl80211/cfg80211</B><DD>
|
|
This is the preferred driver for Linux.
|
|
<DT id="84"><B>Linux wireless extensions</B><DD>
|
|
In theory, any driver that supports Linux wireless
|
|
extensions can be used with IEEE 802.1X (i.e., not WPA) when
|
|
using ap_scan=0 option in configuration file.
|
|
<DT id="85"><B>Wired Ethernet drivers</B><DD>
|
|
Use ap_scan=0.
|
|
<DT id="86"><B>BSD net80211 layer (e.g., Atheros driver)</B><DD>
|
|
At the moment, this is for FreeBSD 6-CURRENT branch.
|
|
<DT id="87"><B>Windows NDIS</B><DD>
|
|
The current Windows port requires WinPcap
|
|
(<A HREF="http://winpcap.polito.it/).">http://winpcap.polito.it/).</A> See README-Windows.txt for more
|
|
information.
|
|
</DL>
|
|
<P>
|
|
|
|
wpa_supplicant was designed to be portable for different
|
|
drivers and operating systems. Hopefully, support for more wlan
|
|
cards and OSes will be added in the future. See developer.txt for
|
|
more information about the design of wpa_supplicant and porting to
|
|
other drivers. 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.
|
|
<A NAME="lbAK"> </A>
|
|
<H2>ARCHITECTURE</H2>
|
|
|
|
<P>
|
|
|
|
The
|
|
<B>wpa_supplicant</B> system consists of the following
|
|
components:
|
|
<DL COMPACT>
|
|
<DT id="88"><B></B><I>wpa_supplicant.conf</I><B> </B><DD>
|
|
the configuration file describing all networks that the
|
|
user wants the computer to connect to.
|
|
<DT id="89"><B>wpa_supplicant</B><DD>
|
|
the program that directly interacts with the
|
|
network interface.
|
|
<DT id="90"><B>wpa_cli</B><DD>
|
|
the
|
|
client program that provides a high-level interface to the
|
|
functionality of the daemon.
|
|
<DT id="91"><B>wpa_passphrase</B><DD>
|
|
a utility needed to construct
|
|
<I>wpa_supplicant.conf</I> files that include
|
|
encrypted passwords.
|
|
</DL>
|
|
<A NAME="lbAL"> </A>
|
|
<H2>QUICK START</H2>
|
|
|
|
<P>
|
|
|
|
First, make a configuration file, e.g.
|
|
<I>/etc/wpa_supplicant.conf</I>, that describes the networks
|
|
you are interested in. See <B><A HREF="/cgi-bin/man/man2html?5+wpa_supplicant.conf">wpa_supplicant.conf</A></B>(5)
|
|
for details.
|
|
<P>
|
|
|
|
Once the configuration is ready, you can test whether the
|
|
configuration works by running <B>wpa_supplicant</B>
|
|
with following command to start it on foreground with debugging
|
|
enabled:
|
|
<P>
|
|
<DL COMPACT><DT id="92"><DD>
|
|
<P>
|
|
<PRE>
|
|
wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -d
|
|
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
|
|
Assuming everything goes fine, you can start using following
|
|
command to start <B>wpa_supplicant</B> on background
|
|
without debugging:
|
|
<P>
|
|
<DL COMPACT><DT id="93"><DD>
|
|
<P>
|
|
<PRE>
|
|
wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -B
|
|
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
|
|
Please note that if you included more than one driver
|
|
interface in the build time configuration (.config), you may need
|
|
to specify which interface to use by including -D<driver
|
|
name> option on the command line.
|
|
<A NAME="lbAM"> </A>
|
|
<H2>INTERFACE TO PCMCIA-CS/CARDMRG</H2>
|
|
|
|
<P>
|
|
|
|
For example, following small changes to pcmcia-cs scripts
|
|
can be used to enable WPA support:
|
|
<P>
|
|
|
|
Add MODE="Managed" and WPA="y" to the network scheme in
|
|
<I>/etc/pcmcia/wireless.opts</I>.
|
|
<P>
|
|
|
|
Add the following block to the end of <B>start</B>
|
|
action handler in <I>/etc/pcmcia/wireless</I>:
|
|
<P>
|
|
<DL COMPACT><DT id="94"><DD>
|
|
<P>
|
|
<PRE>
|
|
if [ "$WPA" = "y" -a -x /usr/local/bin/wpa_supplicant ]; then
|
|
/usr/local/bin/wpa_supplicant -B -c/etc/wpa_supplicant.conf -i$DEVICE
|
|
fi
|
|
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
|
|
Add the following block to the end of <B>stop</B>
|
|
action handler (may need to be separated from other actions) in
|
|
<I>/etc/pcmcia/wireless</I>:
|
|
<P>
|
|
<DL COMPACT><DT id="95"><DD>
|
|
<P>
|
|
<PRE>
|
|
if [ "$WPA" = "y" -a -x /usr/local/bin/wpa_supplicant ]; then
|
|
killall wpa_supplicant
|
|
fi
|
|
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
|
|
This will make <B>cardmgr</B> start
|
|
<B>wpa_supplicant</B> when the card is plugged
|
|
in.
|
|
<A NAME="lbAN"> </A>
|
|
<H2>SEE ALSO</H2>
|
|
|
|
<P>
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?8+wpa_background">wpa_background</A></B>(8)
|
|
<B><A HREF="/cgi-bin/man/man2html?5+wpa_supplicant.conf">wpa_supplicant.conf</A></B>(5)
|
|
<B><A HREF="/cgi-bin/man/man2html?8+wpa_cli">wpa_cli</A></B>(8)
|
|
<B><A HREF="/cgi-bin/man/man2html?8+wpa_passphrase">wpa_passphrase</A></B>(8)
|
|
<A NAME="lbAO"> </A>
|
|
<H2>LEGAL</H2>
|
|
|
|
<P>
|
|
|
|
wpa_supplicant is copyright (c) 2003-2019,
|
|
Jouni Malinen <j@w1.fi> and
|
|
contributors.
|
|
All Rights Reserved.
|
|
<P>
|
|
|
|
This program is licensed under the BSD license (the one with
|
|
advertisement clause removed).
|
|
<P>
|
|
|
|
<HR>
|
|
<A NAME="index"> </A><H2>Index</H2>
|
|
<DL>
|
|
<DT id="96"><A HREF="#lbAB">NAME</A><DD>
|
|
<DT id="97"><A HREF="#lbAC">SYNOPSIS</A><DD>
|
|
<DT id="98"><A HREF="#lbAD">OVERVIEW</A><DD>
|
|
<DT id="99"><A HREF="#lbAE">SUPPORTED FEATURES</A><DD>
|
|
<DT id="100"><A HREF="#lbAF">AVAILABLE DRIVERS</A><DD>
|
|
<DT id="101"><A HREF="#lbAG">COMMAND LINE OPTIONS</A><DD>
|
|
<DT id="102"><A HREF="#lbAH">EXAMPLES</A><DD>
|
|
<DT id="103"><A HREF="#lbAI">OS REQUIREMENTS</A><DD>
|
|
<DT id="104"><A HREF="#lbAJ">SUPPORTED DRIVERS</A><DD>
|
|
<DT id="105"><A HREF="#lbAK">ARCHITECTURE</A><DD>
|
|
<DT id="106"><A HREF="#lbAL">QUICK START</A><DD>
|
|
<DT id="107"><A HREF="#lbAM">INTERFACE TO PCMCIA-CS/CARDMRG</A><DD>
|
|
<DT id="108"><A HREF="#lbAN">SEE ALSO</A><DD>
|
|
<DT id="109"><A HREF="#lbAO">LEGAL</A><DD>
|
|
</DL>
|
|
<HR>
|
|
This document was created by
|
|
<A HREF="/cgi-bin/man/man2html">man2html</A>,
|
|
using the manual pages.<BR>
|
|
Time: 00:06:18 GMT, March 31, 2021
|
|
</BODY>
|
|
</HTML>
|