From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nft 8/9] doc: ct zone set support
Date: Tue, 14 Mar 2017 20:58:15 +0100 [thread overview]
Message-ID: <20170314195816.1721-9-fw@strlen.de> (raw)
In-Reply-To: <20170314195816.1721-1-fw@strlen.de>
Signed-off-by: Florian Westphal <fw@strlen.de>
---
doc/nft.xml | 28 +++++++++++++++++++++++++++-
1 file changed, 27 insertions(+), 1 deletion(-)
diff --git a/doc/nft.xml b/doc/nft.xml
index de86d2a18258..8ea280417742 100644
--- a/doc/nft.xml
+++ b/doc/nft.xml
@@ -3347,6 +3347,7 @@ ip6 filter output log flags all
<group choice="req">
<arg>mark</arg>
<arg>label</arg>
+ <arg>zone</arg>
</group>
<arg choice="none">set</arg>
<replaceable>value</replaceable>
@@ -3354,10 +3355,14 @@ ip6 filter output log flags all
</para>
<para>
The ct statement sets meta data associated with a connection.
+ The zone id has to be assigned before a conntrack lookup takes place,
+ i.e. this has to be done in prerouting and possibly output (if locally
+ generated packets need to be placed in a distinct zone), with a hook
+ priority of -300.
</para>
<para>
<table frame="all">
- <title>Meta statement types</title>
+ <title>Conntrack statement types</title>
<tgroup cols='3' align='left' colsep='1' rowsep='1'>
<colspec colname='c1'/>
<colspec colname='c2'/>
@@ -3380,6 +3385,12 @@ ip6 filter output log flags all
<entry>Connection tracking label</entry>
<entry>label</entry>
</row>
+ <row>
+ <entry>zone</entry>
+ <entry>conntrack zone</entry>
+ <entry>integer (16 bit)</entry>
+ </row>
+
</tbody>
</tgroup>
</table>
@@ -3391,6 +3402,21 @@ ip6 filter output log flags all
ct set mark meta mark
</programlisting>
</example>
+ <example>
+ <title>set zone mapped via interface</title>
+ <programlisting>
+table inet raw {
+ chain prerouting {
+ type filter hook prerouting priority -300;
+ ct zone set iif map { "eth1" : 1, "veth1" : 2 }
+ }
+ chain output {
+ type filter hook output priority -300;
+ ct zone set oif map { "eth1" : 1, "veth1" : 2 }
+ }
+}
+ </programlisting>
+ </example>
</para>
</refsect2>
<refsect2>
--
2.10.2
next prev parent reply other threads:[~2017-03-14 19:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 19:58 [PATCH nft 0/9] ct helper set support Florian Westphal
2017-03-14 19:58 ` [PATCH nft 1/9] src: add initial ct helper support Florian Westphal
2017-03-14 19:58 ` [PATCH nft 2/9] evaluate: refactor CMD_OBJ_QUOTA/COUNTER handling Florian Westphal
2017-03-14 19:58 ` [PATCH nft 3/9] src: allow listing all ct helpers Florian Westphal
2017-03-14 19:58 ` [PATCH nft 4/9] src: implement add/create/delete for ct helper objects Florian Westphal
2017-03-14 19:58 ` [PATCH nft 5/9] ct: add conntrack event mask support Florian Westphal
2017-03-14 20:00 ` Florian Westphal
2017-03-15 9:53 ` Pablo Neira Ayuso
2017-03-14 19:58 ` [PATCH nft 6/9] tests: py: add ct helper tests Florian Westphal
2017-03-15 10:39 ` Pablo Neira Ayuso
2017-03-15 11:46 ` Florian Westphal
2017-03-14 19:58 ` [PATCH nft 7/9] files: provide 'raw' table equivalent Florian Westphal
2017-03-14 19:58 ` Florian Westphal [this message]
2017-03-14 19:58 ` [PATCH nft 9/9] doc: helper assignement Florian Westphal
2017-03-15 10:40 ` Pablo Neira Ayuso
2017-03-15 10:35 ` [PATCH nft 0/9] ct helper set support 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=20170314195816.1721-9-fw@strlen.de \
--to=fw@strlen.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 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).