From: Holger Eitzenberger <heitzenberger@astaro.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH] add TCP protocol state event groups
Date: Mon, 02 Jul 2007 11:40:54 +0200 [thread overview]
Message-ID: <4688C826.4020404@astaro.com> (raw)
In-Reply-To: <4677DB3F.8010901@trash.net>
Patrick McHardy wrote:
>> This patch adds per-protocol state event groups, so one can only listen to a
>> certain TCP state change such as ESTABLISHED. Although such per-state message
>> filtering could be done in userspace, we save CPU cycles since the kernel does
>> not need to build and delivery messages that will be later discarded in
>> userspace. This patch is particularly useful for conntrackd.
> I can see that this is useful, but one group per protocol state
> sounds rather excessive, I would expect that we could group them
> more logically, maybe "connection setup, teardown and updates"?
> Which states is conntrackd particulary interested in?
> I would also like to hear from Holger whether his conntrack daemon
> could make use of a mechnism like this too and if the filtering
> capabilities you propose will do.
Hi :)
Sorry for my late answer, but I am currently rather busy with other stuff.
ctsyncd currently does quite some per-protocol filtering, e.g. TCP
connections currently get synced only after being in the ESTABLISHED
state and deleted on the slave side if the teardown event is received.
This greatly reduces the number of events which are send to the ctsyncd
peer.
Although ctsyncd does not have a performance problem at all even if I
run it against our Spirent performance system I generally like the idea
of doing some of the filtering in kernelspace. Though I would leave the
userspace filtering code as a fallback solution in place.
As of July I have a new colleague which hopefully takes over some of the
workloads I currently have. My plan therefore for ctsyncd is to finally
improve filtering capability of ctsyncd and make if configurable, as
currently most of the filtering code is still hardcoded. My plan is
also to improve the partnership with keepalived et all, basically making
this part more configurable too. This version will then be my 1.0
release, as it currently runs fine for serveral months now on our ASG
products.
So hopefully I am able to release ctsyncd 1.0 into the public within the
next few weeks, especially with Netfilter Workshop in mind.
Hope that helps.
/holger
--
Holger Eitzenberger <heitzenberger@astaro.com> | Kernel Developer
Astaro AG | www.astaro.com | Phone +49-721-25516-246 | Fax -200
Download your free 30 day trial version of the award-winning Astaro
Security Gateway solution here: https://my.astaro.com/download/
next prev parent reply other threads:[~2007-07-02 9:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 18:05 [PATCH] add TCP protocol state event groups Pablo Neira Ayuso
2007-06-19 13:33 ` Patrick McHardy
2007-06-19 14:13 ` Pablo Neira Ayuso
2007-06-19 14:44 ` Patrick McHardy
2007-06-20 17:17 ` Pablo Neira Ayuso
2007-06-20 17:40 ` Patrick McHardy
2007-06-21 15:47 ` Pablo Neira Ayuso
2007-06-21 16:04 ` Patrick McHardy
2007-06-21 19:11 ` states worth to replicate [was Re: [PATCH] add TCP protocol state event groups] Pablo Neira Ayuso
2007-06-22 12:49 ` Patrick McHardy
2007-07-02 9:40 ` Holger Eitzenberger [this message]
2007-07-02 15:36 ` [PATCH] add TCP protocol state event groups 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=4688C826.4020404@astaro.com \
--to=heitzenberger@astaro.com \
--cc=kaber@trash.net \
--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.