tests: validate generated netlink instructions

compare netlink instructions generated by given nft command line
with recorded version.

Example: udp dport 80 accept in ip family should look like

ip test-ip4 input
  [ payload load 1b @ network header + 9 => reg 1 ]
  [ cmp eq reg 1 0x00000011 ]
  [ payload load 2b @ transport header + 2 => reg 1 ]
  [ cmp eq reg 1 0x00005000 ]
  [ immediate reg 0 accept ]

This is stored in udp.t.payload.ip

Other suffixes:
.payload.ip6
.payload.inet
.payload ('any')

The test script first looks for 'testname.t.payload.$family', if that
doesn't exist 'testname.t.payload' is used.

This allows for family independent test (e.g. meta), where we don't
expect/have any family specific expressions.

Signed-off-by: Florian Westphal <fw@strlen.de>

1 files changed, 24 insertions, 0 deletions

diff --git a/tests/regression/any/queue.t.payload b/tests/regression/any/queue.t.payload
new file mode 100644
index 00000000..43a6650c
--- /dev/null
+++ b/tests/regression/any/queue.t.payload
@@ -0,0 +1,24 @@
+# queue
+ip test-ip4 output
+  [ queue num 0]
+
+# queue num 2
+ip test-ip4 output
+  [ queue num 2]
+
+# queue num 2-3
+ip test-ip4 output
+  [ queue num 2-3]
+
+# queue num 4-5 fanout bypass
+ip test-ip4 output
+  [ queue num 4-5 bypass fanout]
+
+# queue num 4-5 fanout
+ip test-ip4 output
+  [ queue num 4-5 fanout]
+
+# queue num 4-5 bypass
+ip test-ip4 output
+  [ queue num 4-5 bypass]
+