From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: [nft PATCH] tests: shell: Prevent lockout in nft-f/0008split_tables_0
Date: Tue, 21 Nov 2017 23:13:39 +0100 [thread overview]
Message-ID: <20171121221339.32090-1-phil@nwl.cc> (raw)
In-Reply-To: <20171121170946.GB24866@breakpoint.cc>
Since packets traverse both tables, the accept rule in the first one is
ineffective due to the second table's drop policy. To prevent lockouts
when running the testsuite via SSH connection, set the second chain's
policy to accept as well.
Fixes: 337c7e0de3d9d ("tests: shell: make sure split table definition works via nft -f")
Signed-off-by: Phil Sutter <phil@nwl.cc>
---
tests/shell/testcases/nft-f/0008split_tables_0 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/shell/testcases/nft-f/0008split_tables_0 b/tests/shell/testcases/nft-f/0008split_tables_0
index 2bc6e46c852a6..dd03545b172ac 100755
--- a/tests/shell/testcases/nft-f/0008split_tables_0
+++ b/tests/shell/testcases/nft-f/0008split_tables_0
@@ -19,7 +19,7 @@ RULESET="table inet filter {
table inet filter {
chain input {
- type filter hook input priority 1; policy drop;
+ type filter hook input priority 1; policy accept;
}
}"
@@ -37,7 +37,7 @@ EXPECTED="table inet filter {
}
chain input {
- type filter hook input priority 1; policy drop;
+ type filter hook input priority 1; policy accept;
}
}"
--
2.13.1
next prev parent reply other threads:[~2017-11-21 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 11:15 nftables: lockout with 0008split_tables_0 test Phil Sutter
2017-11-21 17:09 ` Florian Westphal
2017-11-21 18:39 ` Arturo Borrero Gonzalez
2017-11-21 18:50 ` Arturo Borrero Gonzalez
2017-11-21 22:13 ` Phil Sutter [this message]
2017-11-22 12:17 ` [nft PATCH] tests: shell: Prevent lockout in nft-f/0008split_tables_0 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=20171121221339.32090-1-phil@nwl.cc \
--to=phil@nwl.cc \
--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).