1IWEVENT(8) Linux Programmer's Manual IWEVENT(8)
2
6 iwevent - Display Wireless Events generated by drivers and setting
7 changes
8
10 iwevent
11
13 iwevent displays Wireless Events received through the RTNetlink socket.
14 Each line displays the specific Wireless Event which describes what has
15 happened on the specified wireless interface.
16 This command doesn't take any arguments.
17
19 There are two classes of Wireless Events.
20 The first class is events related to a change of wireless settings on
22 the interface (typically done through iwconfig or a script calling
23 iwconfig). Only settings that could result in a disruption of connec‐
24 tivity are reported. The events currently reported are changing one of
25 the following setting :
26 Network ID
27 ESSID
28 Frequency
29 Mode
30 Encryption
31 All those events will be generated on all wireless interfaces by the
32 kernel wireless subsystem (but only if the driver has been converted to
33 the new driver API).
34 The second class of events are events generated by the hardware, when
36 something happens or a task has been finished. Those events include :
37 New Access Point/Cell address
39 The interface has joined a new Access Point or Ad-Hoc Cell, or
40 lost its association with it. This is the same address that is
41 reported by iwconfig.
42 Scan request completed
44 A scanning request has been completed, results of the scan are
45 available (see iwlist).
46 Tx packet dropped
48 A packet directed at this address has been dropped because the
49 interface believes this node doesn't answer anymore (usually
50 maximum of MAC level retry exceeded). This is usually an early
51 indication that the node may have left the cell or gone out of
52 range, but it may be due to fading or excessive contention.
53 Custom driver event
55 Event specific to the driver. Please check the driver documenta‐
56 tion.
57 Registered node
59 The interface has successfully registered a new wireless
60 client/peer. Will be generated mostly when the interface acts as
61 an Access Point (mode Master).
62 Expired node
64 The registration of the client/peer on this interface has
65 expired. Will be generated mostly when the interface acts as an
66 Access Point (mode Master).
67 Spy threshold crossed
69 The signal strength for one of the addresses in the spy list
70 went under the low threshold or went above the high threshold.
71 Most wireless drivers generate only a subset of those events, not all
73 of them, the exact list depends on the specific hardware/driver combi‐
74 nation. Please refer to driver documentation for details on when they
75 are generated, and use iwlist(8) to check what the driver supports.
76
78 Jean Tourrilhes - jt@hpl.hp.com
79
81 iwconfig(8), iwlist(8), iwspy(8), iwpriv(8), wireless(7).
82net-tools 23 June 2004 IWEVENT(8)