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 6/8][CTNETLINK] Rework conntrack fields dumping logic on events
Date: Tue, 08 Aug 2006 12:45:00 +0200 [thread overview]
Message-ID: <44D86B2C.80006@trash.net> (raw)
In-Reply-To: <44C61C17.5040800@netfilter.org>
Pablo Neira Ayuso wrote:
> + /*
> + * What do we dump on conntrack events? Good question,
> + * the following table should clarify 8)
> + *
> + * | NEW | UPDATE | DESTROY |
> + * ----------------------------------------|
> + * tuples | Y | Y | Y |
> + * status | Y | Y | N |
> + * timeout | Y | Y | N |
> + * protoinfo | Y | Y | N |
> + * helper | S | S | N |
> + * counters | N | N | Y |
> + * mark | S | S | N |
> + *
> + * Leyend:
> + * Y: yes
> + * N: no
> + * S: iif the field is set
> + */
> +
I think this is a bit excessive, the code pretty much speaks for itself.
prev parent reply other threads:[~2006-08-08 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 13:26 [PATCH 6/8][CTNETLINK] Rework conntrack fields dumping logic on events Pablo Neira Ayuso
2006-08-08 10:45 ` 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=44D86B2C.80006@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.