From: Amin Azez <azez@ufomechanic.net>
To: netfilter-devel@lists.netfilter.org
Cc: Harald Welte <laforge@netfilter.org>, Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH 1/*] nfnetlink updates
Date: Wed, 13 Jul 2005 09:04:14 +0100 [thread overview]
Message-ID: <42D4CAFE.90802@ufomechanic.net> (raw)
In-Reply-To: <42D42975.8070303@eurodev.net>
Pablo Neira wrote:
> Hi,
>
> This patch introduces the following changes to nfnetlink:
>
> a) nfnetlink groups: Up to 32 maximum.
>
> +#define NF_NETLINK_CONNTRACK_NEW 0x1
> +#define NF_NETLINK_CONNTRACK_UPDATE 0x2
> +#define NF_NETLINK_CONNTRACK_DESTROY 0x4
> +#define NF_NETLINK_CONNTRACK_EXPECT 0x8
>
> I think that those four groups are enough to group events.
Currently there are about 3 netlink packets sent when a connection comes
up and three when it goes down.
I wonder if it is worth being able to filter on the ctstate as well,
under heavy load it is quite a benefit to reduce the netlink throughput
by 3 times. An application might be interested in ESTABLISHED and CLOSE
or TIMEOUT states.
These are subsets of CONNTRACK_UPDATE
I don't feel _very_ strongly about this, but I do think it is worth
mentioning.
Amin
next prev parent reply other threads:[~2005-07-13 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 20:35 [PATCH 1/*] nfnetlink updates Pablo Neira
2005-07-13 8:04 ` Amin Azez [this message]
2005-07-17 22:38 ` Harald Welte
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=42D4CAFE.90802@ufomechanic.net \
--to=azez@ufomechanic.net \
--cc=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.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.