1 .\" Jean Tourrilhes - HPL - 2002
4 .TH IWEVENT 8 "25 January 2002" "net-tools" "Linux Programmer's Manual"
9 iwevent \- Display Wireless Events generated by drivers and setting changes
21 display Wireless Events received through the RTNetlink socket. Each
22 line display the specific Wireless Event which describe what has
23 happened on the specified wireless interface.
25 This command doesn't take any arguments.
30 There is two classes of Wireless Events.
32 The first class is events related to a change of wireless settings on
33 the interface (typically done through
37 Only settings that could result in a disruption of connectivity are
38 reported. The events currently reported are changing one of the
51 All those events will be generated on all wireless interfaces by the
52 kernel wireless subsystem (but only if the driver has been converted
53 to the new driver API).
55 The second class of events are events generated by the hardware, when
56 something happens or a task has been finished. Those events include :
58 .B New Access Point/Cell address
59 The interface has joined a new Access Point or Ad-Hoc Cell, or lost
60 its association with it. This is the same MAC address that is reported
64 .B Scan request completed
65 A scanning request has been completed, results of the scan are
70 A packet directed at this address has been dropped because the
71 interface believes this node doesn't answer anymore. An early
72 indication that the node may have left the cell or gone out of range.
74 .B Custom driver event
75 Event specific to the driver. Please check the driver documentation.
78 The interface has successfully registered a new wireless
79 client/peer. Will be generated mostly when the interface act as an
80 Access Point (mode master).
83 The registration of the client/peer on this interface has
84 expired. Will be generated mostly when the interface act as an Access
87 Only some of those events will be generated on some wireless
88 interfaces by the wireless driver, and their support depend on the
89 specific hardware/driver combination. Please refer to driver
90 documentation for details.
95 Jean Tourrilhes \- jt@hpl.hp.com