From: Harald Welte <laforge@netfilter.org>
To: Pablo Neira <pablo@eurodev.net>
Cc: Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH 1/*] nfnetlink updates
Date: Sun, 17 Jul 2005 22:38:22 +0000 (UTC)
Date: Tue, 19 Jul 2005 11:48:42 +0200 [thread overview]
Message-ID: <20050719094842.GA3768@rama> (raw)
In-Reply-To: <42D42975.8070303@eurodev.net>
[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]
Hi Pablo, thanks for your patches.
On Tue, Jul 12, 2005 at 10:35:01PM +0200, Pablo Neira wrote:
> 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.
>
> d) NFNL_SUBSYS_CTNETLINK_EXP has been killed. This is superseded by the group
> NF_NETLINK_CONNTRACK_EXPECT.
>
Patrick and me have just discussed this subject, and we thought it would
be better to only have the first three groups and keep the expectations
in their own subsys. This seems more orthogonal, so the group tells you
the kind of event (new/update/destroy), and the subsystem indicates
conntrack/expect.
> e) nfnetlink_subsystem internal list isn't used, the array is enough.
great.
Ok, so with the minor change above, I think all of the changes are fine.
I've just reworked the conntrack event cache to work without requiring
skb->nfcache. I'll try to merge all the code and produce some working
version which I'll put in svn.
--
- Harald Welte <laforge@netfilter.org> http://netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-07-17 22:38 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
2005-07-17 22:38 ` Harald Welte [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=20050719094842.GA3768@rama \
--to=laforge@netfilter.org \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@eurodev.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 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.