From: Simon Lodal <simonl@parknet.dk>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] Document --state UNTRACKED
Date: Tue, 4 May 2010 10:04:08 +0200 [thread overview]
Message-ID: <201005041004.08349.simonl@parknet.dk> (raw)
In-Reply-To: <alpine.LSU.2.01.1005040913330.9626@obet.zrqbmnf.qr>
Tirsdag 04 maj 2010 09:13:43 skrev Jan Engelhardt:
> On Tuesday 2010-05-04 08:32, Simon Lodal wrote:
> >--state UNTRACKED was missing in man page.
>
> As is --ctstate UNTRACKED
Were you aiming for this, or just making a remark?
Signed-off-by: Simon Lodal <simonl@parknet.dk>
diff -ruNp a/extensions/libxt_conntrack.man b/extensions/libxt_conntrack.man
--- a/extensions/libxt_conntrack.man 2010-03-01 15:11:28.000000000 +0100
+++ b/extensions/libxt_conntrack.man 2010-05-04 09:57:47.000000000 +0200
@@ -55,6 +55,10 @@ in both directions,
meaning that the packet is starting a new connection, but is associated with an
existing connection, such as an FTP data transfer, or an ICMP error.
.TP
+\fBUNTRACKED\fR
+meaning that the packet is not tracked at all, which happens if you use
+the NOTRACK target in mangle table.
+.TP
\fBSNAT\fR
A virtual state, matching if the original source address differs from the reply
destination.
diff -ruNp a/extensions/libxt_state.man b/extensions/libxt_state.man
--- a/extensions/libxt_state.man 2010-03-01 15:11:28.000000000 +0100
+++ b/extensions/libxt_state.man 2010-05-04 09:57:47.000000000 +0200
@@ -19,3 +19,6 @@ directions, and
meaning that the packet is starting a new connection, but is
associated with an existing connection, such as an FTP data transfer,
or an ICMP error.
+.B UNTRACKED
+meaning that the packet is not tracked at all, which happens if you use
+the NOTRACK target in mangle table.
next prev parent reply other threads:[~2010-05-04 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 6:32 [PATCH] Document --state UNTRACKED Simon Lodal
2010-05-04 7:13 ` Jan Engelhardt
2010-05-04 8:04 ` Simon Lodal [this message]
2010-05-04 9:48 ` Pascal Hambourg
2010-05-04 10:05 ` Simon Lodal
2010-05-09 23:03 ` Pablo Neira Ayuso
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=201005041004.08349.simonl@parknet.dk \
--to=simonl@parknet.dk \
--cc=jengelh@medozas.de \
--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 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.