From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Mart Frauenlob <mart.frauenlob@chello.at>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] conntrack: Add missing tables dying and unconfirmed to usage output.
Date: Thu, 7 Apr 2016 19:47:48 +0200 [thread overview]
Message-ID: <20160407174748.GA7271@salvia> (raw)
In-Reply-To: <57069951.8080706@chello.at>
On Thu, Apr 07, 2016 at 07:30:57PM +0200, Mart Frauenlob wrote:
> On 07.04.2016 11:45, Pablo Neira Ayuso wrote:
> >also applied.
> >
>
> I'd update the man page also, but I'm unsure about the wording.
> Is there a description of the tables dying and unconfirmed
> somewhere in the source? Or maybe someone can help me out with a
> brief description?
Let me give it a try:
'dying' shows the conntrack entries that have expired and that have been
destroyed by the connection tracking itself or via the conntrack
utility.
'unconfirmed' shows new entries that are not yet inserted into the
conntrack table, these entries are attached to packets that are
traversing the stack, but that did not reach the confirmation point at
the postrouting hook.
These two new tables are basically only useful for debugging purposes.
Under normal operation, it is hard to see entries in any of these two
tables.
Well, to be preciuse, there are still two "normal cases" where you
could see entries there: 1) when packets that are enqueued via
nfqueue, or 2) when conntrackd runs in event reliable mode. But these
are kind of corner cases where it is valid to see entries in the
unconfirmed table.
Feel free to reword/improve/adapt it for the manpage.
prev parent reply other threads:[~2016-04-07 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 9:43 [PATCH] conntrack: Add missing tables dying and unconfirmed to usage output Mart Frauenlob
2016-04-07 9:45 ` Pablo Neira Ayuso
2016-04-07 17:30 ` Mart Frauenlob
2016-04-07 17:47 ` Pablo Neira Ayuso [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=20160407174748.GA7271@salvia \
--to=pablo@netfilter.org \
--cc=mart.frauenlob@chello.at \
--cc=netfilter-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).