Update to v30-pre9

[android-x86/external-wireless-tools.git] / wireless_tools / iwevent.8

diff --git a/wireless_tools/iwevent.8 b/wireless_tools/iwevent.8
index 719e131..02a98e0 100644 (file)
--- a/wireless_tools/iwevent.8
+++ b/wireless_tools/iwevent.8
@@ -1,7 +1,7 @@
-.\" Jean Tourrilhes - HPL - 2002
+.\" Jean Tourrilhes - HPL - 2002 - 2004
 .\" iwevent.8
 .\"
-.TH IWEVENT 8 "25 January 2002" "net-tools" "Linux Programmer's Manual"
+.TH IWEVENT 8 "23 June 2004" "net-tools" "Linux Programmer's Manual"
 .\"
 .\" NAME part
 .\"
@@ -18,8 +18,8 @@ iwevent \- Display Wireless Events generated by drivers and setting changes
 .\"
 .SH DESCRIPTION
 .B iwevent
-display Wireless Events received through the RTNetlink socket. Each
-line display the specific Wireless Event which describe what has
+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.
@@ -27,7 +27,7 @@ This command doesn't take any arguments.
 .\" DISPLAY part
 .\"
 .SH DISPLAY
-There is two classes of Wireless Events.
+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
@@ -57,7 +57,7 @@ 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 MAC address that is reported
+its association with it. This is the same address that is reported
 by
 .BR iwconfig .
 .TP
@@ -68,26 +68,34 @@ available (see
 .TP
 .B 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.
+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 act as an
-Access Point (mode master).
+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 act as an Access
-Point (mode master).
+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
-Only some of those events will be generated on some wireless
-interfaces by the wireless driver, and their support depend on the
-specific hardware/driver combination. Please refer to driver
-documentation for details.
+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
 .\"
@@ -98,6 +106,7 @@ Jean Tourrilhes \- jt@hpl.hp.com
 .\"
 .SH SEE ALSO
 .BR iwconfig (8),
-.BR ifconfig (8),
+.BR iwlist (8),
 .BR iwspy (8),
-.BR iwpriv (8).
+.BR iwpriv (8),
+.BR wireless (7).