Package: argus-server Version: 1:2.0.6.fixes.1-10 Severity: normal
The argus.conf file as deployed has an option called ARGUS_MONITOR_DATA, typically set to `hostname`. This can be set with a name of ARGUS_MONITOR_ID instead, and is set this way in the current source distribution for argus. The peculiar side effect of the current configuration is that argus logs the occasional informational message with a bogus IP address, "229.97.122.203" on a couple of systems I have here. I added a line to argus.conf with ARGUS_MONITOR_ID instead, though hard-coded in my case to contain the IP address. This now reports correctly in the argus.log file. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.5 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages argus-server depends on: ii debconf [debconf-2.0] 1.4.66 Debian configuration management sy ii libc6 2.3.5-9 GNU C Library: Shared libraries an ii libpcap0.7 0.7.2-7 System interface for user-level pa ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra ii logrotate 3.7.1-2 Log rotation utility ii net-tools 1.60-17 The NET-3 networking toolkit Versions of packages argus-server recommends: ii argus-client 2.0.6.fixes.1-2 IP network transaction auditing to -- debconf information: * argus/overwrite_conffile: true * argus/startup: boot -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
