similar to: [Bug 921] New: log, ulog and nflog: command-line parameters are not supported

http://bugzilla.netfilter.org/show_bug.cgi?id=748 Summary: Range check for ulog-cprange is wrong Product: iptables Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: iptables AssignedTo: netfilter-buglog at lists.netfilter.org ReportedBy:

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

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:

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=977 Netbug <b1b30ee4 at opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #27 from Netbug <b1b30ee4 at opayq.com>

I''ve opened up development of Shorewall 4.1. While I had previously announced that Shorewall 4.1 would focus on IPv6, I have since learned that the netfilter team are developing ''xtables'', a unified IP0v4/IPv6 utility. It seems silly to spend the effort to add Shorewall support for IPv6 only to then have to turn around and convert it to use xtables. So I''ve

http://bugzilla.netfilter.org/show_bug.cgi?id=723 Summary: extensions/libxt_NFLOG.man definines invalid range for - -nflog-group Product: iptables Version: CVS (please indicate timestamp) Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P5 Component: iptables

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

https://bugzilla.netfilter.org/show_bug.cgi?id=977 --- Comment #25 from Netbug <b1b30ee4 at opayq.com> --- Oh crap maybe I did screw this up, I didn't realize I needed to change a group. So you're saying it's showing it on 0 now and it needs to be on 1? I remember reading this before; Use NFLOG as your log level, and as with ULOG you can specify the group NFLOG(1,0,1). NFLOG

https://bugzilla.netfilter.org/show_bug.cgi?id=977 Eric Leblond <eric at regit.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #26 from Eric Leblond <eric at

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

Hello, I tried Shorewall for the first time today. I am currently using an up-to-date installation of Debian Sid, which has shorewall 4.2.10, shorewall-shell 4.2.10 and shorewall-perl 4.2.10.1. I noticed that even though I had the following /etc/shorewall/policy file, iptables would still show LOG rules at the end of the INPUT and OUTPUT chains instead of ULOG rules. (Other logging related rules

https://bugzilla.netfilter.org/show_bug.cgi?id=1232 Bug ID: 1232 Summary: Ulogd2 Failed Startup on VPS Product: ulogd Version: SVN (please provide timestamp) Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: major Priority: P5 Component: ulogd Assignee:

Hi, I''ve just recently switched off my (lame) hardware firewall onto an old box running linux 2.4.18, iptables 1.2.6 and shorewall 1.2.9. I''m kinda new to linux firewalling myself but so far Shorewall has taken much work from me. While reading myself into iptables I saw that just recently something called ULOG (userspace logging) has been implemented in newer kernels and

--/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=652 Mariusz Kielpinski <kielpi at poczta.onet.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kielpi at poczta.onet.pl Status|ASSIGNED |NEW --- Comment #3 from

I''m noticing some weirdness in my ulog files with version 2.0.10. Here is a portion of the log: Jan 7 11:01:37 rancor Shorewall:loc2fw:AllowWOL: IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:0a:95:b2:11:4c:08:00 SRC=192.168.0.100 DST=192.168.0.255 LEN=97 TOS=00 PREC=0x00 TTL=64 ID=44155 CE PROTO=UDP SPT=631 DPT=631 LEN=77 Jan 7 11:01:39 rancor Shorewall:loc2fw:AllowWOL: IN=eth1 OUT=

hi, if i would like to use ulog (in order to split netfilter messages from other kernel messages), than i have to set all loglevel to ULOG? and then is there any way to define diferent loglevel for eg. maclist? thanks in advance. yours. ps. it''s a bit confusing that all loglevel parameter name is LOG_LEVEL except BLACKLIST_LOGLEVEL:-( -- Levente

Hi! The Netfilter project proudly presents: iptables 1.4.14 This release several bugfixes and support for the new cttimeout infrastructure. This allows you to attach specific timeout policies to flow via iptables CT target. The following example shows the usage of this new infrastructure in a couple of steps: 1) Create a timeout policy with name `custom-tcp-policy1': nfct

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