similar to: New Shorewall user trying to get ulogd setup

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

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

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=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:

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=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

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 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.

http://shorewall.net/pub/shorewall/Alpha/shorewall-2.0.0 ftp://shorewall.net/pub/shorewall/Alpha/shorewall-2.0.0 See if this change to proxy arp is more palatable. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

--/aVve/J9H4Wl5yVO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Everybody! I had to change the ulog.patch in recent patch-o-matic to use a different netlink family (it's now 5 instead of 4). This means, you will have to recompile your ulogd or any other application in order to make it work. That's also why I have

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

--+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

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

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

--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,

I would like to cut down on packets logged from "loc2net". I have modified my policy file so that the logging for loc2net is "err" but dns packets and smtp are still being logged. Is it possible to filter these out? On a separate note, if I define ULOG in policy, I get an error on shorewall startup "ULOG not defined" or something of that nature. Sorry about being

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

Dear all, I have configured both shorewall and shorewall6 on my firewall. Shorewall is using ULOG as logging target and since that did not seem to work I tried using NFLOG in shorewall6. However, nothing is logged in the /var/log files. Three questions: - What am I doing wrong? I just use LOG=NFLOG in the params file. - Can I use NFLOG for shorewall too? - Do I need ulogd when setting the

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 [re]start" has been speeded up by more than 40% with my