Since I got no responses to my query about stopping iptables from
logging crud to the ring buffer (dmesg output) I decided to give ulogd
a try. Unfortunately it logs absolutely nothing but start/stop
messages to /var/log/ulogd.log. I know that ulogd used to require a
kernel patch, but thought this has changed in the 2.4.18 kernel, which
is what I'm running. 

Is anyone else using ulogd with a 2.4.18 kernel? What was involved in
getting it to log iptables output? Did you have to apply a kernel
patch? I have ULOG as a target in my iptables setup script, and I can
replace ULOG with LOG and get output (to just about everything, dmesg
output, console, syslog, etc., which is why I'm trying ulogd), so I
know the rules are acting the way they're supposed to.

I'm stumped. Any help appreciated.

Gary


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to