From 2efbdf7b8fcf79f3fa8a6471d2eca00df0c91108 Mon Sep 17 00:00:00 2001 From: Florian Westphal Date: Wed, 9 May 2018 12:18:20 +0200 Subject: tests: py: allow to specify sets with a timeout Not usable yet, as the set timeout netlink output isn't captured so far, but it adds groundwork to add this as a follow-up. Set definition syntax changes a little, if you want to add multiple elements they now have to be separated by "," just like in nftables. Signed-off-by: Florian Westphal --- tests/py/ip/sets.t | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'tests/py/ip/sets.t') diff --git a/tests/py/ip/sets.t b/tests/py/ip/sets.t index 658579aa..7b7e0722 100644 --- a/tests/py/ip/sets.t +++ b/tests/py/ip/sets.t @@ -14,19 +14,19 @@ ?set1 192.168.3.4;ok ?set1 192.168.3.4;ok -?set1 192.168.3.5 192.168.3.6;ok -?set1 192.168.3.5 192.168.3.6;ok -?set1 192.168.3.8 192.168.3.9;ok -?set1 192.168.3.10 192.168.3.11;ok +?set1 192.168.3.5, 192.168.3.6;ok +?set1 192.168.3.5, 192.168.3.6;ok +?set1 192.168.3.8, 192.168.3.9;ok +?set1 192.168.3.10, 192.168.3.11;ok ?set1 1234:1234:1234:1234:1234:1234:1234:1234;fail ?set2 192.168.3.4;fail !set2 type ipv4_addr;ok ?set2 192.168.3.4;ok -?set2 192.168.3.5 192.168.3.6;ok -?set2 192.168.3.5 192.168.3.6;ok -?set2 192.168.3.8 192.168.3.9;ok -?set2 192.168.3.10 192.168.3.11;ok +?set2 192.168.3.5, 192.168.3.6;ok +?set2 192.168.3.5, 192.168.3.6;ok +?set2 192.168.3.8, 192.168.3.9;ok +?set2 192.168.3.10, 192.168.3.11;ok ip saddr @set1 drop;ok ip saddr != @set1 drop;ok -- cgit v1.2.3