similar to: [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol

https://bugzilla.netfilter.org/show_bug.cgi?id=977 --- Comment #6 from Netbug <b1b30ee4 at opayq.com> --- I upgraded to ulogd 2.0.4 & kernel 3.17.2 but these did not make a difference, here's how the output looks now; Sat Nov 1 17:07:03 2014 <5> ulogd.c:843 building new pluginstance stack:

https://bugzilla.netfilter.org/show_bug.cgi?id=977 --- Comment #29 from Netbug <b1b30ee4 at opayq.com> --- Hi Eric, So it's ok to use; stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU With #bind=1 commented out? I thought if you're going to use log2 then bind=1 had to be uncommented? -- You are receiving this mail because: You are watching

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:

http://bugzilla.netfilter.org/show_bug.cgi?id=665 Bruno Friedmann <bruno at ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #9 from Bruno Friedmann <bruno at

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

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 --- Comment #21 from Eric Leblond <eric at regit.org> --- Hello, (In reply to Netbug from comment #20) > Hi Eric, > > The new log; iptables-save_nflog_2 and the output I pasted for, > > cat /proc/net/netfilter/nf_log; > > All this is good now? All i see in the iptables rules regarding NFLOG is: -A INPUT -j NFLOG

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

http://bugzilla.netfilter.org/show_bug.cgi?id=595 eric at inl.fr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Comment #3 from eric at inl.fr 2009-12-14 20:31 ------- With

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=977 --- Comment #14 from Eric Leblond <eric at regit.org> --- (In reply to Netbug from comment #11) > Hi Eric, > > Thanks for getting back to me, really appreciate it. > > I'm not using NFLOG at the moment, so let me know if the iptables-save is > ok, without using it at the moment, along with the cat? OK, I really need

https://bugzilla.netfilter.org/show_bug.cgi?id=977 --- Comment #22 from Netbug <b1b30ee4 at opayq.com> --- In shorewall I have NFLOG listed for the shorewall.conf and the policy file, this is the only place I put in the word NFLOG... Please see these attachements... -- You are receiving this mail because: You are watching all bug changes. -------------- next part -------------- An HTML

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=977 --- Comment #11 from Netbug <b1b30ee4 at opayq.com> --- Hi Eric, Thanks for getting back to me, really appreciate it. I'm not using NFLOG at the moment, so let me know if the iptables-save is ok, without using it at the moment, along with the cat? I've attached two logs for each... thanks -- You are receiving this mail

https://bugzilla.netfilter.org/show_bug.cgi?id=977 --- Comment #15 from Netbug <b1b30ee4 at opayq.com> --- Ok I was thinking this so I set everything back to NFLOG, I've attached; iptables-save_nflog Here's the cat /proc/net/netfilter/nf_log; 0 NONE (nfnetlink_log) 1 NONE (nfnetlink_log) 2 nfnetlink_log (nf_log_ipv4,nfnetlink_log) 3 NONE (nfnetlink_log) 4 NONE

https://bugzilla.netfilter.org/show_bug.cgi?id=977 --- Comment #28 from Eric Leblond <eric at regit.org> --- Hello, (In reply to Netbug from comment #27) > Hi Eric, > ... > > So I thought you mentioned I need to have bind=1 uncommented? But it creates > these messags, so maybe there's still something going on here, and not a > user error at this point? Well

https://bugzilla.netfilter.org/show_bug.cgi?id=1218 Bug ID: 1218 Summary: ULOGD PCAP Plugin Missing Ethernet Headers Product: ulogd Version: SVN (please provide timestamp) Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 Component: ulogd Assignee:

Hi! The Netfilter project proudly presents: ulogd 2.0.0 ulogd is a userspace logging daemon for netfilter/iptables related logging. This includes per-packet logging of security violations, per-packet logging for accounting, per-flow logging and flexible user-defined accounting. ulogd was almost entirely written by Harald Welte, with contributions from fellow hackers such as Pablo Neira

https://bugzilla.netfilter.org/show_bug.cgi?id=977 --- Comment #30 from Netbug <b1b30ee4 at opayq.com> --- What I meant to also say, I thought when using log2 bind=1 was suppose to be uncommented was the correct way to use ulog.log? So this is why I'm confused now, like I'm using the setting in ulog.log incorrect and it's working... -- You are receiving this mail because: You

https://bugzilla.netfilter.org/show_bug.cgi?id=977 --- Comment #5 from Netbug <b1b30ee4 at opayq.com> --- I'm now using Shorewall 4.6.4.3, but I don't think it makes a difference. I was thinking to try kernel 3.17,2, but not sure it's going to make any difference either. I'm not sure how this is a configuration error, I've tried everything with no positive results,