path: root/tests/shell/testcases/chains
diff options
authorPhil Sutter <>2019-10-21 18:51:14 +0200
committerPhil Sutter <>2019-10-21 22:36:31 +0200
commit9fc71bc6b602c8706d1214e0100bcd7638c257e3 (patch)
tree202156a0aa736d8d31f313d324602b67b9d5ec49 /tests/shell/testcases/chains
parente33b971f35cbfc3634dba9690537bbfb8baeac87 (diff)
main: Fix for misleading error with negative chain priority
getopt_long() would try to parse the negative priority as an option and return -1 as it is not known: | # nft add chain x y { type filter hook input priority -30\; } | nft: invalid option -- '3' Fix this by prefixing optstring with a plus character. This instructs getopt_long() to not collate arguments but just stop after the first non-option, leaving the rest for manual handling. In fact, this is just what nft desires: mixing options with nft syntax leads to confusive command lines anyway. Signed-off-by: Phil Sutter <> Acked-by: Pablo Neira Ayuso <>
Diffstat (limited to 'tests/shell/testcases/chains')
1 files changed, 8 insertions, 0 deletions
diff --git a/tests/shell/testcases/chains/0039negative_priority_0 b/tests/shell/testcases/chains/0039negative_priority_0
new file mode 100755
index 00000000..ba17b8cc
--- /dev/null
+++ b/tests/shell/testcases/chains/0039negative_priority_0
@@ -0,0 +1,8 @@
+# Test parsing of negative priority values
+set -e
+$NFT add table t
+$NFT add chain t c { type filter hook input priority -30\; }