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