Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #522
Difficulty: Medium
11,223 = 0x2BD7
True or False?
Linux & Unix Commands - Search Man Pages

wireless(7) [linux man page]

WIRELESS(7)						     Linux Programmer's Manual						       WIRELESS(7)

NAME
wireless - Wireless Tools and Wireless Extensions SYNOPSIS
iwconfig iwpriv -a DESCRIPTION
The Wireless Extensions is an API allowing you manipulate Wireless LAN networking interfaces. It is composed of a variety of tools and configuration files. It is documented in more detail in the Linux Wireless LAN Howto. The Wireless Tools are used to change the configuration of wireless LAN networking interfaces on the fly, to get their current configura- tion, to get statistics and diagnose them. They are described in their own man page, see below for references. Wireless configuration is specific to each Linux distribution. This man page will contain in the future the configuration procedure for a few common distributions. For the time being, check the file DISTRIBUTIONS.txt included with the Wireless Tools package. DEBIAN 3.0 In Debian 3.0 (and later) you can configure wireless LAN networking devices using the network configuration tool ifupdown(8). File : /etc/network/interfaces Form : wireless-<function> <value> wireless-essid Home wireless-mode Ad-Hoc See also : /etc/network/if-pre-up.d/wireless-tools /usr/share/doc/wireless-tools/README.Debian SuSE 8.0 SuSE 8.0 (and later) has integrated wireless configuration in their network scripts. Tool : Yast2 File : /etc/sysconfig/network/wireless /etc/sysconfig/network/ifcfg-* Form : WIRELESS_<function>=<value> WIRELESS_ESSID="Home" WIRELESS_MODE=Ad-Hoc See also : man ifup info scpm ORIGINAL PCMCIA SCRIPTS
If you are using the original configuration scripts from the Pcmcia package, you can use this method. File : /etc/pcmcia/wireless.opts Form : *,*,*,*) ESSID="Home" MODE="Ad-Hoc" ;; See also : /etc/pcmcia/wireless File PCMCIA.txt part of Wireless Tools package AUTHOR
Jean Tourrilhes - jt@hpl.hp.com http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ SEE ALSO
iwconfig(8), iwlist(8), iwspy(8), iwpriv(8), iwevent(8). wireless-tools 4 March 2004 WIRELESS(7)

Check Out this Related Man Page

IWEVENT(8)						     Linux Programmer's Manual							IWEVENT(8)

NAME
iwevent - Display Wireless Events generated by drivers and setting changes SYNOPSIS
iwevent DESCRIPTION
iwevent displays Wireless Events received through the RTNetlink socket. Each line displays the specific Wireless Event which describes what has happened on the specified wireless interface. This command doesn't take any arguments. DISPLAY
There are two classes of Wireless Events. The first class is events related to a change of wireless settings on the interface (typically done through iwconfig or a script calling iwconfig). Only settings that could result in a disruption of connectivity are reported. The events currently reported are changing one of the following setting : Network ID ESSID Frequency Mode Encryption All those events will be generated on all wireless interfaces by the kernel wireless subsystem (but only if the driver has been converted to the new driver API). The second class of events are events generated by the hardware, when something happens or a task has been finished. Those events include : New Access Point/Cell address The interface has joined a new Access Point or Ad-Hoc Cell, or lost its association with it. This is the same address that is reported by iwconfig. Scan request completed A scanning request has been completed, results of the scan are available (see iwlist). Tx packet dropped A packet directed at this address has been dropped because the interface believes this node doesn't answer anymore (usually maximum of MAC level retry exceeded). This is usually an early indication that the node may have left the cell or gone out of range, but it may be due to fading or excessive contention. Custom driver event Event specific to the driver. Please check the driver documentation. Registered node The interface has successfully registered a new wireless client/peer. Will be generated mostly when the interface acts as an Access Point (mode Master). Expired node The registration of the client/peer on this interface has expired. Will be generated mostly when the interface acts as an Access Point (mode Master). Spy threshold crossed The signal strength for one of the addresses in the spy list went under the low threshold or went above the high threshold. Most wireless drivers generate only a subset of those events, not all of them, the exact list depends on the specific hardware/driver com- bination. Please refer to driver documentation for details on when they are generated, and use iwlist(8) to check what the driver supports. AUTHOR
Jean Tourrilhes - jt@hpl.hp.com SEE ALSO
iwconfig(8), iwlist(8), iwspy(8), iwpriv(8), wireless(7). net-tools 23 June 2004 IWEVENT(8)

Featured Tech Videos