From: Phil Oester <kernel@linuxace.com>
To: netfilter-devel@vger.kernel.org
Cc: pablo@netfilter.org
Subject: [PATCH] nftables: adjust example file for new chain type syntax
Date: Fri, 29 Nov 2013 12:32:29 -0800 [thread overview]
Message-ID: <20131129203228.GB22533@home> (raw)
[-- Attachment #1: Type: text/plain, Size: 102 bytes --]
Example file has not been updated with new syntax.
Signed-off-by: Phil Oester <kernel@linuxace.com>
[-- Attachment #2: patch-nft-example --]
[-- Type: text/plain, Size: 427 bytes --]
diff --git a/files/examples/sets_and_maps b/files/examples/sets_and_maps
index 8dfe9f8..adfc688 100755
--- a/files/examples/sets_and_maps
+++ b/files/examples/sets_and_maps
@@ -37,7 +37,7 @@ table filter {
chain input_1 { counter; }
chain input_2 { counter; }
chain input {
- hook NF_INET_LOCAL_IN 0
+ type filter hook input priority 0
# symbolic anonymous sets
meta iif $local_ifs tcp dport $tcp_ports counter
next reply other threads:[~2013-11-29 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 20:32 Phil Oester [this message]
2013-11-30 20:53 ` [PATCH] nftables: adjust example file for new chain type syntax 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=20131129203228.GB22533@home \
--to=kernel@linuxace.com \
--cc=netfilter-devel@vger.kernel.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 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).