Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #985
Difficulty: Medium
386BSD and FreeBSD were both derived from BSD releases.
True or False?
Linux & Unix Commands - Search Man Pages

iwevent(8) [linux man page]

IWEVENT(8)						     Linux Programmer's Manual							IWEVENT(8)

NAME
iwevent - Display Wireless Events generated by drivers and setting changes SYNOPSIS
iwevent DESCRIPTION
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. This command doesn't take any arguments. DISPLAY
There are two classes of Wireless Events. The first class is events related to a change of wireless settings on the interface (typically done through iwconfig or a script calling iwconfig). Only settings that could result in a disruption of connectivity are reported. The events currently reported are changing one of the following setting : Network ID ESSID Frequency Mode Encryption 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). The second class of events are events generated by the hardware, when something happens or a task has been finished. Those events include : 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 iwconfig. Scan request completed A scanning request has been completed, results of the scan are available (see iwlist). 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. Custom driver event Event specific to the driver. Please check the driver documentation. 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). 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). 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. Most wireless drivers generate only a subset of those events, not all of them, the exact list depends on the specific hardware/driver com- bination. Please refer to driver documentation for details on when they are generated, and use iwlist(8) to check what the driver supports. AUTHOR
Jean Tourrilhes - jt@hpl.hp.com SEE ALSO
iwconfig(8), iwlist(8), iwspy(8), iwpriv(8), wireless(7). net-tools 23 June 2004 IWEVENT(8)

Check Out this Related Man Page

IWSPY(8)						     Linux Programmer's Manual							  IWSPY(8)

NAME
iwspy - Get wireless statistics from specific nodes SYNOPSIS
iwspy [interface] iwspy interface [+] DNSNAME | IPADDR | HWADDR [...] iwspy interface off iwspy interface setthr low high iwspy interface getthr DESCRIPTION
Iwspy is used to set a list of addresses to monitor in a wireless network interface and to read back quality of link information for each of those. This information is the same as the one available in /proc/net/wireless : quality of the link, signal strength and noise level. This information is updated each time a new packet is received, so each address of the list adds some overhead in the driver. Note that this functionality works only for nodes part of the current wireless cell, you can not monitor Access Points you are not associ- ated with (you can use Scanning for that) and nodes in other cells. In Managed mode, in most case packets are relayed by the Access Point, in this case you will get the signal strength of the Access Point. For those reasons this functionality is mostly useful in Ad-Hoc and Mas- ter mode. PARAMETERS
You may set any number of addresses up to 8. DNSNAME | IPADDR Set an IP address, or in some cases a DNS name (using the name resolver). As the hardware works with hardware addresses, iwspy will translate this IP address through ARP. In some case, this address might not be in the ARP cache and iwspy will fail. In those case, ping(8) this name/address and retry. HWADDR Set a hardware (MAC) address (this address is not translated & checked like the IP one). The address must contain a colon (:) to be recognised as a hardware address. + Add the new set of addresses at the end of the current list instead of replacing it. The address list is unique for each device, so each user should use this option to avoid conflicts. off Remove the current list of addresses and disable the spy functionality setthr Set the low and high signal strength threshold for the iwspy event (for drivers that support it). Every time the signal strength for any of the address monitored with iwspy goes lower than the low threshold or goes higher than the high threshold, a Wireless Event will be generated. This can be used to monitor link outages without having to run iwspy periodically. getthr Retrieve the current low and high signal strength threshold for the iwspy event. FILES
/proc/net/wireless SEE ALSO
iwconfig(8), iwlist(8), iwevent(8), iwpriv(8), wireless(7). net-tools 31 October 1996 IWSPY(8)

Featured Tech Videos