From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter@vger.kernel.org
Subject: [patch] iptables.8 - add UNTRACKED state
Date: Fri, 27 Nov 2009 21:05:09 +0100 [thread overview]
Message-ID: <4B1030F5.7030702@chello.at> (raw)
[-- Attachment #1: Type: text/plain, Size: 221 bytes --]
Hello,
I hope the diff is useful. It adds the UNTRACKED state to the state and
conntrack --ctstate descriptions.
diff -cB /usr/local/src/iptables-1.4.5/iptables.8 /tmp/iptables.8 >
iptables.8.diff
Best regards
Mart
[-- Attachment #2: iptables.8.diff --]
[-- Type: text/plain, Size: 1287 bytes --]
*** /usr/local/src/iptables-1.4.5/iptables.8 2009-10-19 19:50:25.000000000 +0200
--- /tmp/iptables.8 2009-11-27 20:45:08.000000000 +0100
***************
*** 607,614 ****
.PP
States for \fB\-\-ctstate\fP:
.TP
\fBINVALID\fR
! meaning that the packet is associated with no known connection
.TP
\fBNEW\fR
meaning that the packet has started a new connection, or otherwise associated
--- 607,618 ----
.PP
States for \fB\-\-ctstate\fP:
.TP
+ \fBUNTRACKED\fR
+ meaning that the packet will not to be tracked by connection tracking.
+ This state can be set using the \fBNOTRACK\fP target.
+ .TP
\fBINVALID\fR
! meaning that the packet is associated with no known connection.
.TP
\fBNEW\fR
meaning that the packet has started a new connection, or otherwise associated
***************
*** 1189,1194 ****
--- 1193,1201 ----
[\fB!\fP] \fB\-\-state\fP \fIstate\fP
Where state is a comma separated list of the connection states to
match. Possible states are
+ .B UNTRACKED
+ meaning that the packet will not to be tracked by connection tracking.
+ This state can be set using the \fBNOTRACK\fP target.
.B INVALID
meaning that the packet could not be identified for some reason which
includes running out of memory and ICMP errors which don't correspond to any
reply other threads:[~2009-11-27 20:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B1030F5.7030702@chello.at \
--to=mart.frauenlob@chello.at \
--cc=netfilter@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.