nexmon – Blame information for rev 1

Subversion Repositories:
Rev:
Rev Author Line No. Line
1 office 1 .\" Jean Tourrilhes - HPL - 2002 - 2004
2 .\" iwevent.8
3 .\"
4 .TH IWEVENT 8 "23 June 2004" "net-tools" "Linux Programmer's Manual"
5 .\"
6 .\" NAME part
7 .\"
8 .SH NAME
9 iwevent \- Display Wireless Events generated by drivers and setting changes
10 .\"
11 .\" SYNOPSIS part
12 .\"
13 .SH SYNOPSIS
14 .BI "iwevent "
15 .br
16 .\"
17 .\" DESCRIPTION part
18 .\"
19 .SH DESCRIPTION
20 .B iwevent
21 displays Wireless Events received through the RTNetlink socket. Each
22 line displays the specific Wireless Event which describes what has
23 happened on the specified wireless interface.
24 .br
25 This command doesn't take any arguments.
26 .\"
27 .\" DISPLAY part
28 .\"
29 .SH DISPLAY
30 There are two classes of Wireless Events.
31 .PP
32 The first class is events related to a change of wireless settings on
33 the interface (typically done through
34 .B iwconfig
35 or a script calling
36 .BR iwconfig ).
37 Only settings that could result in a disruption of connectivity are
38 reported. The events currently reported are changing one of the
39 following setting :
40 .br
41 .I " Network ID"
42 .br
43 .I " ESSID"
44 .br
45 .I " Frequency"
46 .br
47 .I " Mode"
48 .br
49 .I " Encryption"
50 .br
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).
54 .PP
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 :
57 .TP
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 address that is reported
61 by
62 .BR iwconfig .
63 .TP
64 .B Scan request completed
65 A scanning request has been completed, results of the scan are
66 available (see
67 .BR iwlist ).
68 .TP
69 .B Tx packet dropped
70 A packet directed at this address has been dropped because the
71 interface believes this node doesn't answer anymore (usually maximum
72 of MAC level retry exceeded). This is usually an early indication that
73 the node may have left the cell or gone out of range, but it may be
74 due to fading or excessive contention.
75 .TP
76 .B Custom driver event
77 Event specific to the driver. Please check the driver documentation.
78 .TP
79 .B Registered node
80 The interface has successfully registered a new wireless
81 client/peer. Will be generated mostly when the interface acts as an
82 Access Point (mode Master).
83 .TP
84 .B Expired node
85 The registration of the client/peer on this interface has
86 expired. Will be generated mostly when the interface acts as an Access
87 Point (mode Master).
88 .TP
89 .B Spy threshold crossed
90 The signal strength for one of the addresses in the spy list went
91 under the low threshold or went above the high threshold.
92 .PP
93 Most wireless drivers generate only a subset of those events, not all
94 of them, the exact list depends on the specific hardware/driver
95 combination. Please refer to driver documentation for details on when
96 they are generated, and use
97 .IR iwlist (8)
98 to check what the driver supports.
99 .\"
100 .\" AUTHOR part
101 .\"
102 .SH AUTHOR
103 Jean Tourrilhes \- jt@hpl.hp.com
104 .\"
105 .\" SEE ALSO part
106 .\"
107 .SH SEE ALSO
108 .BR iwconfig (8),
109 .BR iwlist (8),
110 .BR iwspy (8),
111 .BR iwpriv (8),
112 .BR wireless (7).