946 lines
23 KiB
HTML
946 lines
23 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML><HEAD><TITLE>Man page of IWCONFIG</TITLE>
|
|
</HEAD><BODY>
|
|
<H1>IWCONFIG</H1>
|
|
Section: Linux Programmer's Manual (8)<BR>Updated: 30 March 2006<BR><A HREF="#index">Index</A>
|
|
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
|
|
|
|
|
|
|
|
|
<A NAME="lbAB"> </A>
|
|
<H2>NAME</H2>
|
|
|
|
iwconfig - configure a wireless network interface
|
|
|
|
|
|
|
|
<A NAME="lbAC"> </A>
|
|
<H2>SYNOPSIS</H2>
|
|
|
|
<B>iwconfig [</B><I>interface</I><B>]</B>
|
|
|
|
<BR>
|
|
|
|
<B>iwconfig </B><I>interface</I><B> [essid </B><I>X</I><B>] [nwid </B><I>N</I><B>] [mode </B><I>M</I><B>] [freq </B><I>F</I><B>]</B>
|
|
|
|
<BR>
|
|
|
|
<B> [channel </B><I>C</I><B>]</B><I>[sens</I><B> S ]</B><I>[ap</I><B> A ]</B><I>[nick</I><B> NN ]</B>
|
|
|
|
<BR>
|
|
|
|
<B> [rate </B><I>R</I><B>] [rts </B><I>RT</I><B>] [frag </B><I>FT</I><B>] [txpower </B><I>T</I><B>]</B>
|
|
|
|
<BR>
|
|
|
|
<B> [enc </B><I>E</I><B>] [key </B><I>K</I><B>] [power </B><I>P</I><B>] [retry </B><I>R</I><B>]</B>
|
|
|
|
<BR>
|
|
|
|
<B> [modu </B><I>M</I><B>] [commit]</B>
|
|
|
|
<BR>
|
|
|
|
<B>iwconfig --help</B>
|
|
|
|
<BR>
|
|
|
|
<B>iwconfig --version</B>
|
|
|
|
|
|
|
|
|
|
<A NAME="lbAD"> </A>
|
|
<H2>DESCRIPTION</H2>
|
|
|
|
<B>Iwconfig</B>
|
|
|
|
is similar to
|
|
<I><A HREF="/cgi-bin/man/man2html?8+ifconfig">ifconfig</A></I>(8),
|
|
|
|
but is dedicated to the wireless interfaces. It is used to set the
|
|
parameters of the network interface which are specific to the wireless
|
|
operation (for example : the frequency).
|
|
<B>Iwconfig</B>
|
|
|
|
may also be used to display those parameters, and the wireless
|
|
statistics (extracted from
|
|
<I>/proc/net/wireless</I>).
|
|
|
|
<P>
|
|
|
|
All these parameters and statistics are device dependent. Each driver
|
|
will provide only some of them depending on hardware support, and the
|
|
range of values may change. Please refer to the man page of each
|
|
device for details.
|
|
|
|
|
|
|
|
<A NAME="lbAE"> </A>
|
|
<H2>PARAMETERS</H2>
|
|
|
|
<DL COMPACT>
|
|
<DT id="1"><B>essid</B>
|
|
|
|
<DD>
|
|
Set the ESSID (or Network Name - in some products it may also be
|
|
called Domain ID). The ESSID is used to identify cells which are part
|
|
of the same virtual network.
|
|
<BR>
|
|
|
|
As opposed to the AP Address or NWID which define a single cell, the
|
|
ESSID defines a group of cells connected via repeaters or
|
|
infrastructure, where the user may roam transparently.
|
|
<BR>
|
|
|
|
With some cards, you may disable the ESSID checking (ESSID
|
|
promiscuous) with
|
|
<I>off</I> or <I>any</I> (and <I>on</I>
|
|
|
|
to reenable it).
|
|
<BR>
|
|
|
|
If the ESSID of your network is one of the special keywords
|
|
(<I>off</I>, <I>on</I> or <I>any</I>),
|
|
|
|
you should use
|
|
<I>--</I>
|
|
|
|
to escape it.
|
|
<BR>
|
|
|
|
<B>Examples :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 essid any</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 essid My Network</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 essid -- ANY</I>
|
|
|
|
<DT id="2"><B>nwid</B>
|
|
|
|
<DD>
|
|
Set the Network ID. As all adjacent wireless networks share the same<BR>
|
|
medium, this parameter is used to differentiate them (create logical
|
|
colocated networks) and identify nodes belonging to the same cell.
|
|
<BR>
|
|
|
|
This parameter is only used for pre-802.11 hardware, the 802.11
|
|
protocol uses the ESSID and AP Address for this function.
|
|
<BR>
|
|
|
|
With some cards, you may disable the Network ID checking (NWID
|
|
promiscuous) with
|
|
<I>off</I> (and <I>on</I>
|
|
|
|
to reenable it).
|
|
<BR>
|
|
|
|
<B>Examples :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 nwid AB34</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 nwid off</I>
|
|
|
|
<DT id="3"><B>nick</B>[name]
|
|
|
|
<DD>
|
|
Set the nickname, or the station name. Some 802.11 products do define<BR>
|
|
it, but this is not used as far as the protocols (MAC, IP, TCP) are
|
|
concerned and completely useless as far as configuration goes. Only
|
|
some wireless diagnostic tools may use it.
|
|
<BR>
|
|
|
|
<B>Example :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 nickname My Linux Node</I>
|
|
|
|
<DT id="4"><B>mode</B>
|
|
|
|
<DD>
|
|
Set the operating mode of the device, which depends on the network<BR>
|
|
topology. The mode can be
|
|
<I>Ad-Hoc</I>
|
|
|
|
(network composed of only one cell and without Access Point),
|
|
<I>Managed</I>
|
|
|
|
(node connects to a network composed of many Access Points, with roaming),
|
|
<I>Master</I>
|
|
|
|
(the node is the synchronisation master or acts as an Access Point),
|
|
<I>Repeater</I>
|
|
|
|
(the node forwards packets between other wireless nodes),
|
|
<I>Secondary</I>
|
|
|
|
(the node acts as a backup master/repeater),
|
|
<I>Monitor</I>
|
|
|
|
(the node is not associated with any cell and passively monitor all
|
|
packets on the frequency) or
|
|
<I>Auto</I>.
|
|
|
|
<BR>
|
|
|
|
<B>Example :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 mode Managed</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 mode Ad-Hoc</I>
|
|
|
|
<DT id="5"><B>freq</B>/<B>channel</B>
|
|
|
|
<DD>
|
|
Set the operating frequency or channel in the device. A value below<BR>
|
|
1000 indicates a channel number, a value greater than 1000 is a
|
|
frequency in Hz. You may append the suffix k, M or G to the value (for
|
|
example, "2.46G" for 2.46 GHz frequency), or add enough '0'.
|
|
<BR>
|
|
|
|
Channels are usually numbered starting at 1, and you may use
|
|
<I><A HREF="/cgi-bin/man/man2html?8+iwlist">iwlist</A></I>(8)
|
|
|
|
to get the total number of channels, list the available frequencies,
|
|
and display the current frequency as a channel. Depending on
|
|
regulations, some frequencies/channels may not be available.
|
|
<BR>
|
|
|
|
When using Managed mode, most often the Access Point dictates the
|
|
channel and the driver may refuse the setting of the frequency. In
|
|
Ad-Hoc mode, the frequency setting may only be used at initial cell
|
|
creation, and may be ignored when joining an existing cell.
|
|
<BR>
|
|
|
|
You may also use
|
|
<I>off</I>
|
|
|
|
or
|
|
<I>auto</I>
|
|
|
|
to let the card pick up the best channel (when supported).
|
|
<BR>
|
|
|
|
<B>Examples :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 freq 2422000000</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 freq 2.422G</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 channel 3</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 channel auto</I>
|
|
|
|
<DT id="6"><B>ap</B>
|
|
|
|
<DD>
|
|
Force the card to register to the Access Point given by the address,<BR>
|
|
if it is possible. This address is the cell identity of the Access
|
|
Point, as reported by wireless scanning, which may be different from
|
|
its network MAC address. If the wireless link is point to point, set
|
|
the address of the other end of the link. If the link is ad-hoc, set
|
|
the cell identity of the ad-hoc network.
|
|
<BR>
|
|
|
|
When the quality of the connection goes too low, the driver may revert
|
|
back to automatic mode (the card selects the best Access Point in
|
|
range).
|
|
<BR>
|
|
|
|
You may also use
|
|
<I>off</I>
|
|
|
|
to re-enable automatic mode without changing the current Access Point,
|
|
or you may use
|
|
<I>any</I>
|
|
|
|
or
|
|
<I>auto</I>
|
|
|
|
to force the card to reassociate with the currently best Access Point.
|
|
<BR>
|
|
|
|
<B>Example :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 ap 00:60:1D:01:23:45</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 ap any</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 ap off</I>
|
|
|
|
<DT id="7"><B>rate</B>/<B>bit</B>[rate]
|
|
|
|
<DD>
|
|
For cards supporting multiple bit rates, set the bit-rate in b/s. The<BR>
|
|
bit-rate is the speed at which bits are transmitted over the medium,
|
|
the user speed of the link is lower due to medium sharing and
|
|
various overhead.
|
|
<BR>
|
|
|
|
You may append the suffix k, M or G to the value (decimal multiplier :
|
|
10^3, 10^6 and 10^9 b/s), or add enough '0'. Values below 1000 are
|
|
card specific, usually an index in the bit-rate list. Use
|
|
<I>auto</I>
|
|
|
|
to select automatic bit-rate mode (fallback to lower rate on noisy
|
|
channels), which is the default for most cards, and
|
|
<I>fixed</I>
|
|
|
|
to revert back to fixed setting. If you specify a bit-rate value and append
|
|
<I>auto</I>,
|
|
|
|
the driver will use all bit-rates lower and equal than this value.
|
|
<BR>
|
|
|
|
<B>Examples :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 rate 11M</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 rate auto</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 rate 5.5M auto</I>
|
|
|
|
<DT id="8"><B>txpower</B>
|
|
|
|
<DD>
|
|
For cards supporting multiple transmit powers, sets the transmit power<BR>
|
|
in dBm. If
|
|
<I>W</I>
|
|
|
|
is the power in Watt, the power in dBm is
|
|
<I>P = 30 + 10.log(W)</I>.
|
|
|
|
If the value is postfixed by
|
|
<I>mW</I>,
|
|
|
|
it will be automatically converted to dBm.
|
|
<BR>
|
|
|
|
In addition,
|
|
<I>on</I> and <I>off</I>
|
|
|
|
enable and disable the radio, and
|
|
<I>auto</I> and <I>fixed</I>
|
|
|
|
enable and disable power control (if those features are available).
|
|
<BR>
|
|
|
|
<B>Examples :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 txpower 15</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 txpower 30mW</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 txpower auto</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 txpower off</I>
|
|
|
|
<DT id="9"><B>sens</B>
|
|
|
|
<DD>
|
|
Set the sensitivity threshold. This define how sensitive is the card<BR>
|
|
to poor operating conditions (low signal, interference). Positive
|
|
values are assumed to be the raw value used by the hardware or a
|
|
percentage, negative values are assumed to be dBm. Depending on the
|
|
hardware implementation, this parameter may control various functions.
|
|
<BR>
|
|
|
|
On modern cards, this parameter usually control handover/roaming
|
|
threshold, the lowest signal level for which the hardware remains
|
|
associated with the current Access Point. When the signal level goes
|
|
below this threshold the card starts looking for a new/better Access
|
|
Point. Some cards may use the number of missed beacons to trigger
|
|
this. For high density of Access Points, a higher threshold make sure
|
|
the card is always associated with the best AP, for low density of
|
|
APs, a lower threshold minimise the number of failed handoffs.
|
|
<BR>
|
|
|
|
On more ancient card this parameter usually controls the defer
|
|
threshold, the lowest signal level for which the hardware considers
|
|
the channel busy. Signal levels above this threshold make the hardware
|
|
inhibits its own transmission whereas signals weaker than this are
|
|
ignored and the hardware is free to transmit. This is usually strongly
|
|
linked to the receive threshold, the lowest signal level for which the
|
|
hardware attempts packet reception. Proper setting of these thresholds
|
|
prevent the card to waste time on background noise while still
|
|
receiving weak transmissions. Modern designs seems to control those
|
|
thresholds automatically.
|
|
<BR>
|
|
|
|
<BR>
|
|
|
|
<B>Example :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 sens -80</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 sens 2</I>
|
|
|
|
<DT id="10"><B>retry</B>
|
|
|
|
<DD>
|
|
Most cards have MAC retransmissions, and some allow to set the<BR>
|
|
behaviour of the retry mechanism.
|
|
<BR>
|
|
|
|
To set the maximum number of retries, enter
|
|
<I>limit `value'</I>.
|
|
|
|
This is an absolute value (without unit), and the default (when
|
|
nothing is specified).
|
|
To set the maximum length of time the MAC should retry, enter
|
|
<I>lifetime `value'</I>.
|
|
|
|
By defaults, this value is in seconds, append the suffix m or u to
|
|
specify values in milliseconds or microseconds.
|
|
<BR>
|
|
|
|
You can also add the
|
|
<I>short</I>, <I>long</I>, <I>min</I> and <I>max</I>
|
|
|
|
modifiers. If the card supports automatic mode, they define the bounds
|
|
of the limit or lifetime. Some other cards define different values
|
|
depending on packet size, for example in 802.11
|
|
<I>min limit</I>
|
|
|
|
is the short retry limit (non RTS/CTS packets).
|
|
<BR>
|
|
|
|
<B>Examples :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 retry 16</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 retry lifetime 300m</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 retry short 12</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 retry min limit 8</I>
|
|
|
|
<DT id="11"><B>rts</B>[_threshold]
|
|
|
|
<DD>
|
|
RTS/CTS adds a handshake before each packet transmission to make sure<BR>
|
|
that the channel is clear. This adds overhead, but increases
|
|
performance in case of hidden nodes or a large number of active
|
|
nodes. This parameter sets the size of the smallest packet for which
|
|
the node sends RTS ; a value equal to the maximum packet size disables
|
|
the mechanism. You may also set this parameter to
|
|
<I>auto</I>, <I>fixed</I> or <I>off</I>.
|
|
|
|
<BR>
|
|
|
|
<B>Examples :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 rts 250</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 rts off</I>
|
|
|
|
<DT id="12"><B>frag</B>[mentation_threshold]
|
|
|
|
<DD>
|
|
Fragmentation allows to split an IP packet in a burst of smaller<BR>
|
|
fragments transmitted on the medium. In most cases this adds overhead,
|
|
but in a very noisy environment this reduces the error penalty and
|
|
allow packets to get through interference bursts. This parameter sets
|
|
the maximum fragment size which is always lower than the maximum
|
|
packet size.
|
|
<BR>
|
|
|
|
This parameter may also control Frame Bursting available on some
|
|
cards, the ability to send multiple IP packets together. This
|
|
mechanism would be enabled if the fragment size is larger than the
|
|
maximum packet size.
|
|
<BR>
|
|
|
|
You may also set this parameter to
|
|
<I>auto</I>, <I>fixed</I> or <I>off</I>.
|
|
|
|
<BR>
|
|
|
|
<B>Examples :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 frag 512</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 frag off</I>
|
|
|
|
<DT id="13"><B>key</B>/<B>enc</B>[ryption]
|
|
|
|
<DD>
|
|
Used to manipulate encryption or scrambling keys and security mode.<BR>
|
|
<BR>
|
|
|
|
To set the current encryption key, just enter the key in hex digits as
|
|
<I>XXXX-XXXX-XXXX-XXXX</I> or <I>XXXXXXXX</I>.
|
|
|
|
To set a key other than the current key, prepend or append
|
|
<I>[index]</I>
|
|
|
|
to the key itself (this won't change which is the active key). You can
|
|
also enter the key as an ASCII string by using the
|
|
<I>s:</I>
|
|
|
|
prefix. Passphrase is currently not supported.
|
|
<BR>
|
|
|
|
To change which key is the currently active key, just enter
|
|
<I>[index]</I>
|
|
|
|
(without entering any key value).
|
|
<BR>
|
|
|
|
<I>off</I> and <I>on</I>
|
|
|
|
disable and reenable encryption.
|
|
<BR>
|
|
|
|
The security mode may be
|
|
<I>open</I>
|
|
|
|
or
|
|
<I>restricted</I>,
|
|
|
|
and its meaning depends on the card used. With most cards, in
|
|
<I>open</I>
|
|
|
|
mode no authentication is used and the card may also accept
|
|
non-encrypted sessions, whereas in
|
|
<I>restricted</I>
|
|
|
|
mode only encrypted sessions are accepted and the card will use
|
|
authentication if available.
|
|
<BR>
|
|
|
|
If you need to set multiple keys, or set a key and change the active
|
|
key, you need to use multiple
|
|
<B>key</B>
|
|
|
|
directives. Arguments can be put in any order, the last one will take
|
|
precedence.
|
|
<BR>
|
|
|
|
<B>Examples :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 key 0123-4567-89</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 key [3] 0123-4567-89</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 key s:password [2]</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 key [2]</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 key open</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 key off</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 key restricted [3] 0123456789</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 key 01-23 key 45-67 [4] key [4]</I>
|
|
|
|
<DT id="14"><B>power</B>
|
|
|
|
<DD>
|
|
Used to manipulate power management scheme parameters and mode.<BR>
|
|
<BR>
|
|
|
|
To set the period between wake ups, enter
|
|
<I>period `value'</I>.
|
|
|
|
To set the timeout before going back to sleep, enter
|
|
<I>timeout `value'</I>.
|
|
|
|
To set the generic level of power saving, enter
|
|
<I>saving `value'</I>.
|
|
|
|
You can also add the
|
|
<I>min</I> and <I>max</I>
|
|
|
|
modifiers. By default, those values are in seconds, append the suffix
|
|
m or u to specify values in milliseconds or microseconds. Sometimes,
|
|
those values are without units (number of beacon periods, dwell,
|
|
percentage or similar).
|
|
<BR>
|
|
|
|
<I>off</I> and <I>on</I>
|
|
|
|
disable and reenable power management. Finally, you may set the power
|
|
management mode to
|
|
<I>all</I>
|
|
|
|
(receive all packets),
|
|
<I>unicast</I>
|
|
|
|
(receive unicast packets only, discard multicast and broadcast) and
|
|
<I>multicast</I>
|
|
|
|
(receive multicast and broadcast only, discard unicast packets).
|
|
<BR>
|
|
|
|
<B>Examples :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 power period 2</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 power 500m unicast</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 power timeout 300u all</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 power saving 3</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 power off</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 power min period 2 power max period 4</I>
|
|
|
|
<DT id="15"><B>modu</B>[lation]
|
|
|
|
<DD>
|
|
Force the card to use a specific set of modulations. Modern cards<BR>
|
|
support various modulations, some which are standard, such as 802.11b
|
|
or 802.11g, and some proprietary. This command force the card to only
|
|
use the specific set of modulations listed on the command line. This
|
|
can be used to fix interoperability issues.
|
|
<BR>
|
|
|
|
The list of available modulations depend on the card/driver and can be
|
|
displayed using
|
|
<I>iwlist modulation</I>.
|
|
|
|
Note that some card/driver may not be able to select each modulation
|
|
listed independently, some may come as a group. You may also set this
|
|
parameter to
|
|
<I>auto</I>
|
|
|
|
let the card/driver do its best.
|
|
<BR>
|
|
|
|
<B>Examples :</B>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 modu 11g</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 modu CCK OFDMa</I>
|
|
|
|
<BR>
|
|
|
|
<I><TT> </TT>iwconfig eth0 modu auto</I>
|
|
|
|
<DT id="16"><B>commit</B>
|
|
|
|
<DD>
|
|
Some cards may not apply changes done through Wireless Extensions<BR>
|
|
immediately (they may wait to aggregate the changes or apply it only
|
|
when the card is brought up via
|
|
<I>ifconfig</I>).
|
|
|
|
This command (when available) forces the card to apply all pending
|
|
changes.
|
|
<BR>
|
|
|
|
This is normally not needed, because the card will eventually apply
|
|
the changes, but can be useful for debugging.
|
|
|
|
|
|
|
|
</DL>
|
|
<A NAME="lbAF"> </A>
|
|
<H2>DISPLAY</H2>
|
|
|
|
For each device which supports wireless extensions,
|
|
<I>iwconfig</I>
|
|
|
|
will display the name of the
|
|
<B>MAC protocol</B>
|
|
|
|
used (name of device for proprietary protocols), the
|
|
<B>ESSID</B>
|
|
|
|
(Network Name), the
|
|
<B>NWID</B>,
|
|
|
|
the
|
|
<B>frequency</B>
|
|
|
|
(or channel), the
|
|
<B>sensitivity</B>,
|
|
|
|
the
|
|
<B>mode</B>
|
|
|
|
of operation, the
|
|
<B>Access Point</B>
|
|
|
|
address, the
|
|
<B>bit-rate</B>,
|
|
|
|
the
|
|
<B>RTS threshold</B>, the <B>fragmentation threshold</B>,
|
|
|
|
the
|
|
<B>encryption key</B>
|
|
|
|
and the
|
|
<B>power management</B>
|
|
|
|
settings (depending on availability).
|
|
<P>
|
|
|
|
The parameters displayed have the same meaning and values as the
|
|
parameters you can set, please refer to the previous part for a
|
|
detailed explanation of them.
|
|
<BR>
|
|
|
|
Some parameters are only displayed in short/abbreviated form (such as
|
|
encryption). You may use
|
|
<I><A HREF="/cgi-bin/man/man2html?8+iwlist">iwlist</A></I>(8)
|
|
|
|
to get all the details.
|
|
<BR>
|
|
|
|
Some parameters have two modes (such as bitrate). If the value is
|
|
prefixed by
|
|
`<B>=</B>',
|
|
|
|
it means that the parameter is fixed and forced to that value, if it
|
|
is prefixed by
|
|
`<B>:</B>',
|
|
|
|
the parameter is in automatic mode and the current value is shown (and
|
|
may change).
|
|
<DL COMPACT>
|
|
<DT id="17"><B>Access Point</B>/<B>Cell</B>
|
|
|
|
<DD>
|
|
An address equal to 00:00:00:00:00:00 means that the card failed to
|
|
associate with an Access Point (most likely a configuration
|
|
issue). The
|
|
<B>Access Point</B>
|
|
|
|
parameter will be shown as
|
|
<B>Cell</B>
|
|
|
|
in ad-hoc mode (for obvious reasons), but otherwise works the same.
|
|
</DL>
|
|
<P>
|
|
|
|
If
|
|
<I>/proc/net/wireless</I>
|
|
|
|
exists,
|
|
<I>iwconfig</I>
|
|
|
|
will also display its content. Note that those values will depend on
|
|
the driver and the hardware specifics, so you need to refer to your
|
|
driver documentation for proper interpretation of those values.
|
|
<DL COMPACT>
|
|
<DT id="18"><B>Link quality</B>
|
|
|
|
<DD>
|
|
Overall quality of the link. May be based on the level of contention
|
|
or interference, the bit or frame error rate, how good the received
|
|
signal is, some timing synchronisation, or other hardware metric. This
|
|
is an aggregate value, and depends totally on the driver and hardware.
|
|
<DT id="19"><B>Signal level</B>
|
|
|
|
<DD>
|
|
Received signal strength (RSSI - how strong the received signal
|
|
is). May be arbitrary units or dBm,
|
|
<I>iwconfig</I>
|
|
|
|
uses driver meta information to interpret the raw value given by
|
|
<I>/proc/net/wireless</I>
|
|
|
|
and display the proper unit or maximum value (using 8 bit arithmetic). In
|
|
<I>Ad-Hoc</I>
|
|
|
|
mode, this may be undefined and you should use
|
|
<I>iwspy</I>.
|
|
|
|
<DT id="20"><B>Noise level</B>
|
|
|
|
<DD>
|
|
Background noise level (when no packet is transmitted). Similar
|
|
comments as for
|
|
<B>Signal level</B>.
|
|
|
|
<DT id="21"><B>Rx invalid nwid</B>
|
|
|
|
<DD>
|
|
Number of packets received with a different NWID or ESSID. Used to
|
|
detect configuration problems or adjacent network existence (on the
|
|
same frequency).
|
|
<DT id="22"><B>Rx invalid crypt</B>
|
|
|
|
<DD>
|
|
Number of packets that the hardware was unable to decrypt. This can be
|
|
used to detect invalid encryption settings.
|
|
<DT id="23"><B>Rx invalid frag</B>
|
|
|
|
<DD>
|
|
Number of packets for which the hardware was not able to properly
|
|
re-assemble the link layer fragments (most likely one was missing).
|
|
<DT id="24"><B>Tx excessive retries</B>
|
|
|
|
<DD>
|
|
Number of packets that the hardware failed to deliver. Most MAC
|
|
protocols will retry the packet a number of times before giving up.
|
|
<DT id="25"><B>Invalid misc</B>
|
|
|
|
<DD>
|
|
Other packets lost in relation with specific wireless operations.
|
|
<DT id="26"><B>Missed beacon</B>
|
|
|
|
<DD>
|
|
Number of periodic beacons from the Cell or the Access Point we have
|
|
missed. Beacons are sent at regular intervals to maintain the cell
|
|
coordination, failure to receive them usually indicates that the card
|
|
is out of range.
|
|
|
|
|
|
|
|
</DL>
|
|
<A NAME="lbAG"> </A>
|
|
<H2>AUTHOR</H2>
|
|
|
|
Jean Tourrilhes - <A HREF="mailto:jt@hpl.hp.com">jt@hpl.hp.com</A>
|
|
|
|
|
|
|
|
<A NAME="lbAH"> </A>
|
|
<H2>FILES</H2>
|
|
|
|
<I>/proc/net/wireless</I>
|
|
|
|
|
|
|
|
|
|
<A NAME="lbAI"> </A>
|
|
<H2>SEE ALSO</H2>
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?8+ifconfig">ifconfig</A></B>(8),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?8+iwspy">iwspy</A></B>(8),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?8+iwlist">iwlist</A></B>(8),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?8+iwevent">iwevent</A></B>(8),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?8+iwpriv">iwpriv</A></B>(8),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?7+wireless">wireless</A></B>(7).
|
|
|
|
<P>
|
|
|
|
<HR>
|
|
<A NAME="index"> </A><H2>Index</H2>
|
|
<DL>
|
|
<DT id="27"><A HREF="#lbAB">NAME</A><DD>
|
|
<DT id="28"><A HREF="#lbAC">SYNOPSIS</A><DD>
|
|
<DT id="29"><A HREF="#lbAD">DESCRIPTION</A><DD>
|
|
<DT id="30"><A HREF="#lbAE">PARAMETERS</A><DD>
|
|
<DT id="31"><A HREF="#lbAF">DISPLAY</A><DD>
|
|
<DT id="32"><A HREF="#lbAG">AUTHOR</A><DD>
|
|
<DT id="33"><A HREF="#lbAH">FILES</A><DD>
|
|
<DT id="34"><A HREF="#lbAI">SEE ALSO</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:13 GMT, March 31, 2021
|
|
</BODY>
|
|
</HTML>
|