ulogd 1.x 2.x deprecated, we going backwards...

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

 



Ok after changing back from ulogd to rsyslog on my Xth server I thought I will write a story about this.

There was once a very nice program called ulogd:

ii ulogd 1.24-3.3 amd64 The Netfilter Userspace Logging Daemon

It was working very nicely for a long time:

[global]

nlgroup=1
logfile="/var/log/firewall/lan.log"
loglevel=1
rmem=131071
bufsize=150000

plugin="/usr/lib/ulogd/ulogd_BASE.so"
plugin="/usr/lib/ulogd/ulogd_LOGEMU.so"

[LOGEMU]
file="/var/log/firewall/lan.log"
sync=1


Up until a day when debian8/9 decided to ship ulogd2:

Package: ulogd2
Version: 2.0.5-5
State: not installed
Priority: optional
Section: net
Maintainer: Chris Boot <bootc@xxxxxxxxxx>
Architecture: amd64
Uncompressed Size: 456 k

Which not just changed the whole config syntax, it doesn't even work anymore with the modern 4.x kernels so I can say it is a fucking piece of shit.

So now on all my new installations I have to rewrite my firewall scripts (which worked for a decade) to log everything through RSYSLOG
then wipe that garbage from the global log.

if $msg contains 'LAN-IN' then /var/log/firewall/lan.log
:msg, contains, "LAN-IN" ~
if $msg contains 'LAN-OUT' then /var/log/firewall/lan.log
:msg, contains, "LAN-OUT" ~

And yay it is almost as good as it was except my machines dmesg are shit around with firewall logs.

So now who to thank this "improvement" over the years?

Couldn't you just leave something which was working as it was you fucking fucktards?
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux