| b.liu | e958203 | 2025-04-17 19:18:16 +0800 | [diff] [blame^] | 1 | .\" Jean Tourrilhes - HPL - 2002 |
| 2 | .\" iwevent.8 |
| 3 | .\" |
| 4 | .TH IWEVENT 8 "25 January 2002" "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 | 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. |
| 24 | .br |
| 25 | This command doesn't take any arguments. |
| 26 | .\" |
| 27 | .\" DISPLAY part |
| 28 | .\" |
| 29 | .SH DISPLAY |
| 30 | There is 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 MAC 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. An early |
| 72 | indication that the node may have left the cell or gone out of range. |
| 73 | .TP |
| 74 | .B Custom driver event |
| 75 | Event specific to the driver. Please check the driver documentation. |
| 76 | .TP |
| 77 | .B Registered node |
| 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). |
| 81 | .TP |
| 82 | .B Expired node |
| 83 | The registration of the client/peer on this interface has |
| 84 | expired. Will be generated mostly when the interface act as an Access |
| 85 | Point (mode master). |
| 86 | .PP |
| 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. |
| 91 | .\" |
| 92 | .\" AUTHOR part |
| 93 | .\" |
| 94 | .SH AUTHOR |
| 95 | Jean Tourrilhes \- jt@hpl.hp.com |
| 96 | .\" |
| 97 | .\" SEE ALSO part |
| 98 | .\" |
| 99 | .SH SEE ALSO |
| 100 | .BR iwconfig (8), |
| 101 | .BR ifconfig (8), |
| 102 | .BR iwspy (8), |
| 103 | .BR iwpriv (8). |