The Aironet docs state:
I have the Aironet set to send all (debugging level) messages to my linux box, and I do see data coming in via tcpdump. I tried this in metalog.conf, but nothing it written to the file:The current software generates the following categories of syslog messages:
Error messages at the emergencies level.
Error messages at the alerts level.
Error messages at the critical level.
Error messages about software or hardware malfunctions, displayed at the errors level.
Interface up/down transitions and system restart messages, displayed at the notification level.
Reload requests and low-process stack messages, displayed at the informational level.
Output from the debug commands, displayed at the debugging level.
Example of Setting Up a UNIX Syslog Daemon
To set up the syslog daemon on a 4.3 BSD UNIX system, include a line such as the following in the file /etc/syslog.conf:
local7.debugging /usr/adm/logs/tiplog
The local7 keyword specifies the logging facility to be used.
The debugging keyword specifies the syslog level. See Table 1 for other keywords that can be listed.
The UNIX system sends messages at or above this level to the specified file, in this case /usr/adm/logs/tiplog. The file must already exist, and the syslog daemon must have permission to write to it.
For the System V UNIX systems, the line should read as follows:
local7.debug /usr/admin/logs/cisco.log
Aironet messages :
facility = "local7"
minimum = 7
logdir = "/var/log/wireless"
Is there somewhere I need to tell metalog to listen to incoming data from other than localhost?
