From d988eb4029e049fcaf3a4f68a076b72cc32c3022 Mon Sep 17 00:00:00 2001 From: Florian Westphal Date: Tue, 13 Feb 2018 15:28:00 +0100 Subject: tests: add test case for sets updated from packet path currently kernel may pick a set implementation that doesn't provide a ->update() function. This causes an error when user attempts to add the nftables rule that is supposed to add entries to the set. Signed-off-by: Florian Westphal --- tests/shell/testcases/sets/0028autoselect_0 | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100755 tests/shell/testcases/sets/0028autoselect_0 (limited to 'tests') diff --git a/tests/shell/testcases/sets/0028autoselect_0 b/tests/shell/testcases/sets/0028autoselect_0 new file mode 100755 index 00000000..fdda832b --- /dev/null +++ b/tests/shell/testcases/sets/0028autoselect_0 @@ -0,0 +1,17 @@ +#!/bin/bash + +# This testscase checks kernel picks a suitable set backends. +# Ruleset attempts to update from packet path, so set backend +# needs an ->update() implementation. + +set -e + +$NFT add table t +$NFT add set t s1 { type inet_proto \; } +$NFT add set t s2 { type ipv4_addr \; } +$NFT add set t s3 { type ipv4_addr \; size 1024\; } +$NFT add chain t c {type filter hook input priority 0 \; } + +$NFT add rule t c meta iifname foobar set add ip protocol @s1 +$NFT add rule t c meta iifname foobar set add ip daddr @s2 +$NFT add rule t c meta iifname foobar set add ip daddr @s3 -- cgit v1.2.3