From: Fred Leeflang <fredl@dutchie.org>
To: netfilter-devel@vger.kernel.org
Cc: vuurmuur-devel@lists.sourceforge.net
Subject: nflog_bind_group() question
Date: Tue, 1 Dec 2009 11:44:12 +0100 [thread overview]
Message-ID: <30defc5b0912010244i385afe45gac6bc521c19a75da@mail.gmail.com> (raw)
Hi devs,
We've recently implemented NFLOG support in vuurmuur, I've written an
article on the effort here
http://wordpress.3dn.nl/2009/11/25/iptabes-nflog-support-in-vuurmuur/
I'm curious about something I found out in the process. I've had
ulogd2 running alongside vuurmuur for a while and configured it to
listen to a specific nflog-group. When I had ulogd2 running I would
not be able to run vuurmuur_log which also listens to an nflog-group.
It took me a while to realize that it would not work because of having
ulogd2 running and both trying to listen to the SAME nflog-group.
Does this mean that it's not possible for two applications at the same
time to get netfilter_log messages from the same nflog-group?
-Fred
next reply other threads:[~2009-12-01 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 10:44 Fred Leeflang [this message]
2009-12-01 10:49 ` nflog_bind_group() question Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30defc5b0912010244i385afe45gac6bc521c19a75da@mail.gmail.com \
--to=fredl@dutchie.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=vuurmuur-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).