From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 7/8][CTNETLINK] send conntrack events on ctnetlink actions
Date: Tue, 08 Aug 2006 12:50:47 +0200 [thread overview]
Message-ID: <44D86C87.20506@trash.net> (raw)
In-Reply-To: <44C61C29.4050202@netfilter.org>
Pablo Neira Ayuso wrote:
> Currently only conntrack events generated by the conntrack core are
> delivered to userspace via ctnetlink. This patch force the generation of
> event notifications on ctnetlink actions.
>
> Example scenario: you have two process listening to ctnetlink and one of
> them creates/changes/destroy a conntrack upon certain events
This doesn't apply without 4/8. I also think sending incremental netlink
updates is questionable here, if no conntrack events are configured
other listeners can only get the entire new state by doing an additional
dump.
prev parent reply other threads:[~2006-08-08 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 13:27 [PATCH 7/8][CTNETLINK] send conntrack events on ctnetlink actions Pablo Neira Ayuso
2006-08-08 10:50 ` Patrick McHardy [this message]
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=44D86C87.20506@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@netfilter.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.