bugzilla-daemon at netfilter.org
2014-Nov-21 17:00 UTC
[Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
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 regit.org> ---
Hello,
(In reply to Netbug from comment #25)> 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 may default to group 0?
>
> NFLOG(1,0,1) - this changes it to the group 1?
This is Shorewall configuration and I don't know it so I can not help.
I'm
closing the bug as it is not related to ulogd. Feel free to reopen if either it
occurs this is not the case.
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.netfilter.org/pipermail/netfilter-buglog/attachments/20141121/bf68bde3/attachment.html>
Seemingly Similar Threads
- [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
- [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
- [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
- [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
- [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
