Displaying 20 results from an estimated 33 matches for "ulogd_inppkt_nflog".
2014 Nov 02
0
[Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
...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> ulogd_inppkt_NFLOG.c:503 forcing unbind of
existing log handler for protocol 7
Sat Nov 1...
2014 Nov 22
0
[Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
...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 log handler for protocol 10
And I noticed that if I commentd out #bind=1 under [log2] then these messages
d...
2014 Oct 30
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 #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,
2014 Nov 02
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 #7 from Netbug <b1b30ee4 at opayq.com> ---
TYPO before;
If you notice you'll see it says log2 on top, then log21 below, both are
getting these messages.
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2014 Nov 02
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 #8 from Netbug <b1b30ee4 at opayq.com> ---
CRAP my typing sorry...
If you notice you'll see it says log2 on top, then LOG1 below...
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2014 Nov 16
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 #9 from Netbug <b1b30ee4 at opayq.com> ---
Hi Eric,
Have you had a chance to look at this?
I know you're probably really busy and have more important things to deal with,
but I could really use some help getting this to work because it doesn't.
This is not a end-user configuration error on my end.
I really need my
2014 Nov 16
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 #10 from Eric Leblond <eric at regit.org> ---
Hi,
Sorry for being so long to answer.
Can you add an iptables-save output to the ticket (or sent it to me privately
if you need to) ? I really don't get what's going on and with that info I will
be able to improve diagnostic and even to reproduce it.
Can you also attache
2014 Nov 17
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 #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
2014 Nov 17
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 #12 from Netbug <b1b30ee4 at opayq.com> ---
Created attachment 455
--> https://bugzilla.netfilter.org/attachment.cgi?id=455&action=edit
iptables-save
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2014 Nov 17
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 #13 from Netbug <b1b30ee4 at opayq.com> ---
Created attachment 456
--> https://bugzilla.netfilter.org/attachment.cgi?id=456&action=edit
nf_log
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2014 Nov 17
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 #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
2014 Nov 17
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 #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
2014 Nov 17
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 #16 from Netbug <b1b30ee4 at opayq.com> ---
Created attachment 457
--> https://bugzilla.netfilter.org/attachment.cgi?id=457&action=edit
iptables-save_nflog
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2014 Nov 17
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 #17 from Netbug <b1b30ee4 at opayq.com> ---
I screwed up the iptables-save_nflog, don't use that one I'm going to brb and
upload a new one, my bad...
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2014 Nov 17
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 #18 from Netbug <b1b30ee4 at opayq.com> ---
Hi Eric,
Grab this one one instead I've attached;
iptables-save_nflog_2
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2014 Nov 17
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 #19 from Netbug <b1b30ee4 at opayq.com> ---
Created attachment 458
--> https://bugzilla.netfilter.org/attachment.cgi?id=458&action=edit
iptables-save_nflog_2
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2014 Nov 20
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 #20 from Netbug <b1b30ee4 at opayq.com> ---
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?
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2014 Nov 21
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 #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
2014 Nov 21
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 #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
2014 Nov 21
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 #23 from Netbug <b1b30ee4 at opayq.com> ---
Created attachment 459
--> https://bugzilla.netfilter.org/attachment.cgi?id=459&action=edit
policy
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: