similar to: [ANNOUNCE] problems with recent ULOG patch and old ulogd

--/aVve/J9H4Wl5yVO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! I've finally managed to install a RedHat 7.3, RedHat 9 and Conectiva 9 on one of my development boxes. This provided the opportunity to build some 'official' iptables-1.2.8 and ulogd-1.0.0 RPM's for the respective distributions. You can get

--J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi All! I have just released a new version of ulogd, the userspace logging deamon meant to be used in combination with the ULOG target of netfilter/iptables patch-o-matic. This new release contains a bugfix, where in certain cases ulogd ran into an endless loop,

--+HwY7O+GdaLKMYOv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! I have finally released Version 1.00 of the iptables userspace logging daemon (ulogd).=20 After being around for almost three years, and receiving lots of positive reports, I have decided to make this new release the 1.00 release, the first official stable

Anywhere that a syslog level can appear, you can now specify ULOG (must be upper case) and logging will occur to the ulog target. You can download ulogd from http://www.gnumonks.org/projects/ulogd. Only the ''firewall'' file is required. None of the comments in the other config files are updated yet but I''m working on it. -Tom -- Tom Eastep \ Shorewall - iptables

FYI. I have not been able to determine 100% that logrotate does this, but ulogd appears to stop logging whenever logrotate runs. So far, the only obvious commonality that I see is that logrotate ran and that the /var/log/ulogd/ulogd.syslogemu is completely empty until I restart ulogd. I have proven that the logging is broken by manually performing a network operation that Shorewall normally

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

hi. ulogd.c use 1.23 as its version while it is shipped with ulog 1.24 moreover ulogd does not log anymore in ulogd.log like ulogd 1.23 did

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:

--mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! I have released Version 1.01 of the iptables userspace logging daemon (ulogd).=20 The new Version is available as tar.bz2 only and can be retrieved from: ftp://ftp.netfilter.org/pub/ulogd/ulogd-1.01.tar.bz2 There is a GPG signature for verification of the

--8P1HSweYDcXXzwPJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! I have just released Version 0.98 of the iptables userspace logging daemon (ulogd). The biggest new features are output plugins for postgresql and pcap. The new Version is available as tar.bz2 only and can be retrieved from:

Hi! I have released version 1.20 of the iptables userspace logging daemon (ulogd). This release is 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 be retrieved from: ftp://ftp.netfilter.org/pub/ulogd/ulogd-1.20.tar.bz2

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

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:

Hi All, I am facing a problem when using ULOG daemon and SNORT (inline mode) with iptables. My set up is like this. 1. I need ULOG daemon to log firewall logs to MYSQL database. 2. I need SNORT in inline mode for intrusion prevention. Both can work fine induvidually with iptables. But ULOG daemon cannot work when SNORT is also running. Probably the reason is that snort also hooks to

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

I am looking for ulog-2.0.x packages and the best I have been able to find [for CentOS6] has been ulog-2.0.0 (which is not an exciting prospect for .0 reasons). Is anyone aware of ulogd packages for CentOS6 [x86_64]? I am kind of surprised this isn't standard fair. -- Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383 Systems Administrator, Python Developer, LPI /

The first public Beta of Shorewall 1.3.12 is now available: New features include: 1) "shorewall refresh" now reloads the traffic shaping rules (tcrules and tcstart). 2) "shorewall debug [re]start" now turns off debugging after an error occurs. This places the point of the failure near the end of the trace rather than up in the middle of it. 3) "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

Dear all: Im using shorewall 2.0.3a (debian) w/ ULOG. shorewall starts ok, and the firewall is running, but nothing is printed on the logs. I try, for example, to do a connection to a port that is opened on the server but closed by the FW and I get a connection refused. If I stop the firewall, this port is accesible from the outside. I think I''ve followed all the steps on

The first Beta Version is available at: http://www.shorewall.net/pub/shorewall/Beta ftp://ftp.shorewall.net/pub/shorewall/Beta New features include: 1) "shorewall refresh" now reloads the traffic shaping rules (tcrules and tcstart). 2) "shorewall debug [re]start" now turns off debugging after an error occurs. This places the point of the failure near the end of the