Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ap-trapd(8) [debian man page]

ap-trapd(8)						      System Manager's Manual						       ap-trapd(8)

NAME
ap-trapd - a SNMP trap processing daemon SYNOPSIS
ap-trapd [ -i device ] [-u user ] [-s] DESCRIPTION
ap-trapd It's a SNMP trap processing daemon that accepts traps, parse them and store useful data using syslog, at logging LEVEL0. Specify device to listen for SNMP traps on the particular device (this option only works at Linux). To be running by user different from nobody you may specify user. To correct work with Smartbridges APs specify -s key (they use specific traps). Utility added to ap-utils from version 0.8. SYSLOG
To store traps to own log file you may add next string to your /etc/syslog.conf local0.* /var/log/ap-traps.log After doing it, just restart syslogd with command like killall -HUP syslogd TRAPS
When a trap is received, a message will be logged indicating that an action happened to the Access Point such as: Trap Reassociation: This trap message is sent when a Station reassociation request is received from Access Point. Trap Association: Indicates the reception of an association request packet and the sender Station's successful association with the Access Point. Trap Disassociation: This trap message is sent when a disassociation notification packet is received from a Station. Trap Reset: This trap message is sent when Access Point Resets. Trap Setting IP Address with Ping: This trap message is sent when the Access Point IP address is set with the transmission of a ping message. Trap Start Up: This trap message is sent when the Access Point Starts Up. Trap Failed To Erase Flash: This trap message is sent when Access Point Failed To Erase Flash. APClientScanning Access Point Client is scanning... APClientAuthenticating Access Point Client is authenticating with the AP. APClientAssociating Access Point Client is associating with the AP. APClientReAssociating Access Point Client is reassociating with the AP. APClientAuthenticationFailed Access Point Client has failed authenticating with the AP. APClientAssociationFailed Access Point Client has failed associating with the AP. APClientConnected Access Point Client has been connected with the AP. APClientDisconnected Access Point Client has been disconnected from the AP. APClientScanFailed Access Point Client has failed scanning! APClientJoinFailed Access Point Client has failed joining! APClientJoining Access Point Client is in join state. Smartbridges specific TRAPS MultiAttachedStation Multiple attached stations in the ethernet size SECURITY Utility ap-trapd must be running by 'root', after opening port utility change owner to 'nobody', so this user must exist in you sys- tem. You may set user using -u option as described below for change default unprivileged user. AUTHOR
Roman Festchook <roma@polesye.net> http://ap-utils.polesye.net SEE ALSO
ap-config(8), ap-mrtg(8), syslogd(8) Wireless Access Point Utilities for Unix ap-trapd(8)

Check Out this Related 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 display Wireless Events received through the RTNetlink socket. Each line display the specific Wireless Event which describe what has happened on the specified wireless interface. This command doesn't take any arguments. DISPLAY
There is 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 MAC 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. An early indica- tion that the node may have left the cell or gone out of range. 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 act 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 act as an Access Point (mode master). 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. AUTHOR
Jean Tourrilhes - jt@hpl.hp.com SEE ALSO
iwconfig(8), ifconfig(8), iwspy(8), iwpriv(8). net-tools 25 January 2002 IWEVENT(8)
Man Page