Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #497
Difficulty: Medium
A computer compiler or interpreter is just as smart as a human.
True or False?
Linux & Unix Commands - Search Man Pages

iwlist(8) [linux man page]

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

NAME
iwlist - Get more detailed wireless information from a wireless interface SYNOPSIS
iwlist [interface] scanning iwlist [interface] frequency iwlist [interface] rate iwlist [interface] keys iwlist [interface] power iwlist [interface] txpower iwlist [interface] retry iwlist [interface] event iwlist [interface] auth iwlist [interface] wpakeys iwlist [interface] genie iwlist [interface] modulation iwlist --help iwlist --version DESCRIPTION
Iwlist is used to display some additional information from a wireless network interface that is not displayed by iwconfig(8). The main argument is used to select a category of information, iwlist displays in detailed form all information related to this category, including information already shown by iwconfig(8). PARAMETERS
scan[ning] Give the list of Access Points and Ad-Hoc cells in range, and optionally a whole bunch of information about them (ESSID, Quality, Frequency, Mode...). The type of information returned depends on what the card supports. Triggering scanning is a privileged operation (root only) and normal users can only read left-over scan results. By default, the way scanning is done (the scope of the scan) is dependant on the card and card settings. This command takes optional arguments, however most drivers will ignore those. The option essid is used to specify a scan on a spe- cific ESSID. With some card/driver, this enables to see hidden networks. The option last does not trigger a scan and read left-over scan results. freq[uency]/channel Give the list of available frequencies in the device and the number of defined channels. Please note that usually the driver returns the total number of channels and only the frequencies available in the present locale, so there is no one-to-one mapping between frequencies displayed and channel numbers. rate/bit[rate] List the bit-rates supported by the device. keys/enc[ryption] List the encryption key sizes supported and list all the encryption keys set in the device. power List the various Power Management attributes and modes of the device. txpower List the various Transmit Powers available on the device. retry List the transmit retry limits and retry lifetime on the device. ap/accesspoint/peers Give the list of Access Points in range, and optionally the quality of link to them. This feature is obsolete and now deprecated in favor of scanning support (above), and most drivers don't support it. Some drivers may use this command to return a specific list of Peers or Access Points, such as the list of Peers associated/regis- tered with the card. See your driver documentation for details. event List the wireless events supported by the device. auth List the WPA authentication parametes curently set. wpa[keys] List all the WPA encryption keys set in the device. genie List the Generic Information Elements set in the device (used for WPA support). modu[lation] List the modulations supported by the device and the modulations currently enabled. --version Display the version of the tools, as well as the recommended and current Wireless Extensions version for the tool and the various wireless interfaces. --help Display short help message. FILES
/proc/net/wireless SEE ALSO
iwconfig(8), iwspy(8). iwevent(8), iwpriv(8), wireless(7). wireless-tools 13 April 2006 IWLIST(8)

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