Displaying 5 results from an estimated 5 matches for "ip2str1".
Did you mean:
ip2str
2014 Nov 02
0
[Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
...- 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:
'log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU'
Sat Nov 1 17:07:03 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind of
existing log handler for protocol 2
Sat Nov 1 17:07:03 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind of
existing log handler for protocol 10
Sat Nov 1 17:07:03 2014 <5...
2009 Dec 14
0
[Bug 595] MARK filter doesn't work
...D
Resolution| |WORKSFORME
------- Comment #3 from eric at inl.fr 2009-12-14 20:31 -------
With latest git tree, I did not manage to reproduce the problem.
For the record, I've used the following stack:
stack=log1:NFLOG,base1:BASE,mark1:MARK,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU
stack=ct1:NFCT,mark1:MARK,op1:OPRINT
--
Configure bugmail: http://bugzilla.netfilter.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
2014 Nov 24
0
[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 #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 all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: &...
2018 Mar 01
0
[Bug 1232] New: Ulogd2 Failed Startup on VPS
...s: man:ulogd(8)
Process: 24095 ExecStart=/usr/sbin/ulogd --daemon --uid ulog --pidfile
/run/ulog/ulogd.pid (code=exited, status=0/SUCCESS)
Main PID: 24096 (code=exited, status=1/FAILURE)
Mar 01 10:36:18 kevus ulogd[24096]: building new pluginstance stack:
'log1:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU'
Mar 01 10:36:18 kevus ulogd[24096]: forcing unbind of existing log handler for
protocol 2
Mar 01 10:36:18 kevus ulogd[24096]: forcing unbind of existing log handler for
protocol 10
Mar 01 10:36:18 kevus ulogd[24096]: forcing unbind of existing log handler for...
2014 Nov 22
0
[Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
...OG(1,0,1)
So I now added in to my shorewall NFLOG(1,0,1), which if I'm understanding this
correct, the first 1 gives me group 1 which I believe is what you said I need.
And now with this setting I'm seeing logging... :)
In ulog.conf I'm using;
stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU
But I noticed I was still getting these messages;
ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 2
ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 7
ulogd_inppkt_NFLOG.c:503 forcing unbind of existing lo...