Software Manual

WE865-DUAL Software User Guide

1vv0300788 Rev. 0 08/08/08

6.4 iwevent

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.

Synopsis

iwevent

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 settings:

Network ID

SSID

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