[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

ulogd-pcap file format not understood by ethereal


the file /var/log/ulog/pcap.log created by ulogd is not understood by
ethereal and tcpdump any more. Even 'file /var/log/ulog/pcap.*' says:

/var/log/ulog/pcap.log:   data
/var/log/ulog/pcap.log.1: tcpdump capture file (little-endian) \
                          - version 2.4 (raw IP, capture length 65536)

The strange thing is that it used to be correctly understood by
ethereal, as can be seen by the logrotated pcap.log.1 above.

The only thing which I changed is to compile the ipfilter modules
statically into the 2.6.5 kernel. However:

> zcat /proc/config.gz | egrep -i "ulog"

/var/log/ulog/pcap.log exists and keeps growing and rules are hit:

# iptables -L -v -n | grep -i ulog
24  672 ULOG icmp -- * * ULOG copy_range 0 nlgroup 1 queue_threshold 1
40 2694 ULOG icmp -- * * ULOG copy_range 0 nlgroup 1 queue_threshold 1

I am using up-to-date sid and kernel-source-2.6.5 which I configured
and compiled myself. The only change I did to /etc/ulogd.conf is to
enable the pcap plugin:

> ar p \
/pub/mirrors/ftp.debian.org/debian/pool/main/u/ulogd/ulogd_1.02-1_i386.deb \
data.tar.gz | tar xOzf - ./etc/ulogd.conf | diff /etc/ulogd.conf -
< plugin /usr/lib/ulogd/ulogd_PCAP.so
> #plugin /usr/lib/ulogd/ulogd_PCAP.so

I stopped ulogd, truncated /var/log/ulog/pcap.log to zero, restarted
ulogd but once it gets filled the data is not understood.

Any hints would be appreciated.


Reply to: