Home Man
Today's Posts

Linux & Unix Commands - Search Man Pages

RedHat 9 (Linux i386) - man page for iwevent (redhat section 8)

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

iwevent - Display Wireless Events generated by drivers and setting changes
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.
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 indication 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 sup- port depend on the specific hardware/driver combination. Please refer to driver documentation for details.
Jean Tourrilhes - jt@hpl.hp.com
iwconfig(8), ifconfig(8), iwspy(8), iwpriv(8). net-tools 25 January 2002 IWEVENT(8)

All times are GMT -4. The time now is 10:56 AM.

Unix & Linux Forums Content Copyrightę1993-2018. All Rights Reserved.
Show Password