similar to: [Bug 1194] New: Kill u 2

http://bugzilla.netfilter.org/show_bug.cgi?id=793 Summary: ulogd -d does not close all fds Product: ulogd Version: SVN (please provide timestamp) Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ulogd AssignedTo: netfilter-buglog at lists.netfilter.org

http://bugzilla.netfilter.org/show_bug.cgi?id=789 Summary: ulog_ct loses outputentries Product: ulogd Version: SVN (please provide timestamp) Platform: i386 OS/Version: Debian GNU/Linux Status: NEW Severity: major Priority: P5 Component: ulogd AssignedTo: netfilter-buglog at lists.netfilter.org

http://bugzilla.netfilter.org/show_bug.cgi?id=791 Summary: SIGUSR2 is undocumented Product: ulogd Version: SVN (please provide timestamp) Platform: All OS/Version: Debian GNU/Linux Status: NEW Severity: enhancement Priority: P5 Component: ulogd AssignedTo: netfilter-buglog at lists.netfilter.org

Hi! I have released version 1.21 of the iptables userspace logging daemon (ulogd). This release is a minur bugfix update to the 'brown paper bag' release 1.20. 1.20 was probably one of the last 'new feature' updates for ulogd, since I'm already working on ulogd2, which includes support for plugin stacks, IPFIX and ct_acct. The new Version is available as tar.bz2 only and can

http://bugzilla.netfilter.org/show_bug.cgi?id=741 Summary: ULOGD segfaults on init Product: ulogd Version: SVN (please provide timestamp) Platform: i386 OS/Version: other Status: NEW Severity: blocker Priority: P5 Component: ulogd_MYSQL AssignedTo: netfilter-buglog at lists.netfilter.org

quick background: RH9 (2.4.20-19.9) Shorewall 1.4.6a-1 ulogd 1.00 Shorewall is working properly. I''ve followed the FAQ instructions and everything appears to be setup correctly. The problem is that I''m trying to get ulog going...but I''m getting: # service ulogd status ulogd dead but subsys locked I''m not sure if I was suppose to, but I also manually created

https://bugzilla.netfilter.org/show_bug.cgi?id=1246 Bug ID: 1246 Summary: Log Product: libnetfilter_log Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: libnetfilter_log Assignee: netfilter-buglog at lists.netfilter.org

I''m trying to get Shorewall to use ulogd for logging, but I''m not seeing any logging in either the file I set up for logs, nor in /var/log/messages (where the logs used to be). I''m running a stock Debian 3.0 woody system, with a custom 2.4.21 kernel. I used all the settings as described on shorewall.net when configuring the kernel. ulogd (0.97-1) and shorewall

Hi Guys I have install ulog and shorewall and edit the shorewall config file to use ulogd for logging, I have also compiled ulogd support into the kernel however I still cannot get shorewall to log through ulogd to file. It keeps dumping info to console. Any assistance would be appreciated. Thanks Craig

https://bugzilla.netfilter.org/show_bug.cgi?id=1191 Bug ID: 1191 Summary: Empty parameters generate errors on iptables-restore, even when saved by iptables-save Product: iptables Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5

Hi List, I read this list for nearly two years and learnt a lot, but now i have a very strange problem I can''t solve.. I have a firewall machine running Debian, which connects a small office to the internet via a DSL-line (with pppoe) and which is running Shorewall. It allows all outbound traffic and accepts pptp, openvpn and ssh-connections (on a non-standard port) from the internet.

https://bugzilla.netfilter.org/show_bug.cgi?id=1131 Bug ID: 1131 Summary: iptables-restore crashes on some fuzzed input Product: iptables Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: iptables-restore Assignee:

http://bugzilla.netfilter.org/show_bug.cgi?id=652 Mariusz Kielpinski <kielpi at poczta.onet.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kielpi at poczta.onet.pl Status|ASSIGNED |NEW --- Comment #3 from

https://bugzilla.netfilter.org/show_bug.cgi?id=986 Bug ID: 986 Summary: ulogd fails to build against linux headers >= 3.17.0 due to ULOG target removal Product: ulogd Version: SVN (please provide timestamp) Hardware: x86_64 OS: Gentoo Status: NEW Severity: major Priority:

https://bugzilla.netfilter.org/show_bug.cgi?id=871 Summary: Running two instances of ulog causes abort in libnfnetlink Product: ulogd Version: SVN (please provide timestamp) Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: ulogd AssignedTo:

http://bugzilla.netfilter.org/show_bug.cgi?id=673 --- Comment #16 from Pablo Neira Ayuso <pablo at netfilter.org> 2011-02-27 20:42:54 --- Have been this issue finally resolved? Please close the bug if so. We're bug hunting to reach final first ulogd 2.0 release. Thanks! -- Configure bugmail: http://bugzilla.netfilter.org/userprefs.cgi?tab=email ------- You are receiving this

Going deeper on last post "[Shorewall-users] logging", I found a very nice package that handles ULOG messages in a web interface, where you can browse the events from a MySql database produced by ULOGD. Real time. The name is: ULOGD-PHP From the site: ------------------------------------------- ulogd-php is able to : show the last hosts that broke packets on your firewall. show the

Hi List, I have just recently set up 2 mint systems with shorewall and have been using the script for a fair amount of time before that. What really ruined my day was the fact that the logging options for the chains'' Policies are in a different place than all the other logging options. I built my kernel with ulogd and spent hours looking for the config options of the policies. Now

https://bugzilla.netfilter.org/show_bug.cgi?id=1240 Bug ID: 1240 Summary: logrotate: file size changed while zipping Product: ulogd Version: SVN (please provide timestamp) Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: normal Priority: P5 Component: ulogd

http://bugzilla.netfilter.org/show_bug.cgi?id=752 Summary: ipq_read() will return an error (rc = -1) and the error message says "Received truncated message" Product: iptables Version: 1.3.5 Platform: i386 OS/Version: RedHat Linux Status: NEW Severity: critical Priority: P1