Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

iwgetid(8) [debian man page]

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

NAME
iwgetid - Report ESSID, NWID or AP/Cell Address of wireless network SYNOPSIS
iwgetid [interface] [--raw] [--scheme] [--ap] [--freq] [--mode] [--protocol] [--channel] DESCRIPTION
iwgetid is used to find out the NWID, ESSID or AP/Cell Address of the wireless network that is currently used. The information reported is the same as the one shown by iwconfig, but iwgetid is easier to integrate in various scripts. By default, iwgetid will print the ESSID of the device, and if the device doesn't have any ESSID it will print its NWID. The default formatting output is pretty-print. OPTIONS
--raw This option disables pretty-printing of the information. This option is orthogonal to the other options (except --scheme), so with the appropriate combination of options you can print the raw ESSID, AP Address or Mode. This format is ideal when storing the result of iwgetid as a variable in Shell or Perl scripts or to pass the result as an argument on the command line of iwconfig. --scheme This option is similar to the previous one, it disables pretty-printing of the information and removes all characters that are not alphanumerics (like space, punctuation and control characters). The resulting output is a valid Pcmcia scheme identifier (that may be used as an argument of the command cardctl scheme). This for- mat is also ideal when using the result of iwgetid as a selector in Shell or Perl scripts, or as a file name. --ap Display the MAC address of the Wireless Access Point or the Cell. --freq Display the current frequency or channel used by the interface. --channel Display the current channel used by the interface. The channel is determined using the current frequency and the frequency list pro- vided by the interface. --mode Display the current mode of the interface. --protocol Display the protocol name of the interface. This allows to identify all the cards that are compatible with each other and accept the same type of configuration. This can also be used to check Wireless Extension support on the interface, as this is the only attribute that all drivers support- ing Wireless Extension are mandated to support. SEE ALSO
iwconfig(8), ifconfig(8), iwspy(8), iwpriv(8). wireless-tools 02 December 2003 IWGETID(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 display Wireless Events received through the RTNetlink socket. Each line display the specific Wireless Event which describe what has happened on the specified wireless interface. This command doesn't take any arguments. DISPLAY
There is 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 MAC 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. An early indica- tion that the node may have left the cell or gone out of range. 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 act 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 act as an Access Point (mode master). Only some of those events will be generated on some wireless interfaces by the wireless driver, and their support depend on the specific hardware/driver combination. Please refer to driver documentation for details. AUTHOR
Jean Tourrilhes - jt@hpl.hp.com SEE ALSO
iwconfig(8), ifconfig(8), iwspy(8), iwpriv(8). net-tools 25 January 2002 IWEVENT(8)
Man Page