summaryrefslogtreecommitdiffstats
path: root/tests/regression/any/ct.t
diff options
context:
space:
mode:
authorArturo Borrero <arturo.borrero.glez@gmail.com>2015-12-11 11:10:14 +0100
committerPablo Neira Ayuso <pablo@netfilter.org>2015-12-15 21:36:14 +0100
commit6b29a5bebb957387fe1aac8fcbfd431e6be237f0 (patch)
tree7e0be595ee6acfbdd2611045a7d227d5f329a16e /tests/regression/any/ct.t
parent564b0e7c13f98b9ad054058137b4c0bb61bd46b4 (diff)
tests/: rearrange tests directory
Rearrange the directory to obtain a better organization of files and tests-suites. We end with a tree like this: tests | .--- py .--- shell .--- files This was suggested by Pablo. Signed-off-by: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'tests/regression/any/ct.t')
-rw-r--r--tests/regression/any/ct.t109
1 files changed, 0 insertions, 109 deletions
diff --git a/tests/regression/any/ct.t b/tests/regression/any/ct.t
deleted file mode 100644
index 059402e2..00000000
--- a/tests/regression/any/ct.t
+++ /dev/null
@@ -1,109 +0,0 @@
-*ip;test-ip4
-*ip6;test-ip6
-*inet;test-inet
-
-:output;type filter hook output priority 0
-
-ct state new,established, related, untracked;ok;ct state established,related,new,untracked
-ct state != related;ok
-ct state {new,established, related, untracked};ok
-- ct state != {new,established, related, untracked};ok
-ct state invalid drop;ok
-ct state established accept;ok
-ct state 8;ok;ct state new
-ct state xxx;fail
-
-ct direction original;ok
-ct direction != original;ok
-ct direction reply;ok
-ct direction != reply;ok
-ct direction {reply, original};ok
-- ct direction != {reply, original};ok
-ct direction xxx;fail
-
-ct status expected;ok
-ct status != expected;ok
-ct status seen-reply;ok
-ct status != seen-reply;ok
-ct status {expected, seen-reply, assured, confirmed, dying};ok
-ct status xxx;fail
-
-# SYMBOL("snat", IPS_SRC_NAT)
-# SYMBOL("dnat", IPS_DST_NAT)
-- ct status snat;ok
-- ct status dnat;ok
-
-ct mark 0;ok;ct mark 0x00000000
-ct mark or 0x23 == 0x11;ok;ct mark | 0x00000023 == 0x00000011
-ct mark or 0x3 != 0x1;ok;ct mark | 0x00000003 != 0x00000001
-ct mark and 0x23 == 0x11;ok;ct mark & 0x00000023 == 0x00000011
-ct mark and 0x3 != 0x1;ok;ct mark & 0x00000003 != 0x00000001
-ct mark xor 0x23 == 0x11;ok;ct mark 0x00000032
-ct mark xor 0x3 != 0x1;ok;ct mark != 0x00000002
-
-ct mark 0x00000032;ok
-ct mark != 0x00000032;ok
-ct mark 0x00000032-0x00000045;ok
-ct mark != 0x00000032-0x00000045;ok
-ct mark {0x32, 0x2222, 0x42de3};ok;ct mark { 0x00042de3, 0x00002222, 0x00000032}
-- ct mark != {0x32, 0x2222, 0x42de3};ok
-
-# ct mark != {0x32, 0x2222, 0x42de3};ok
-# BUG: invalid expression type set
-# nft: src/evaluate.c:975: expr_evaluate_relational: Assertion '0' failed.
-
-ct mark set 0x11 xor 0x1331;ok;ct mark set 0x00001320
-ct mark set 0x11333 and 0x11;ok;ct mark set 0x00000011
-ct mark set 0x12 or 0x11;ok;ct mark set 0x00000013
-ct mark set 0x11;ok;ct mark set 0x00000011
-
-ct expiration 30;ok;ct expiration 30s
-ct expiration 22;ok;ct expiration 22s
-ct expiration != 233;ok;ct expiration != 3m53s
-ct expiration 33-45;ok;ct expiration 33s-45s
-ct expiration != 33-45;ok;ct expiration != 33s-45s
-ct expiration {33, 55, 67, 88};ok;ct expiration { 1m7s, 33s, 55s, 1m28s}
-- ct expiration != {33, 55, 67, 88};ok;ct expiration { 1m7s, 33s, 55s, 1m28s}
-ct expiration {33-55};ok;ct expiration { 33s-55s}
-# BUG: ct expiration {33-55}
-# Broken output: ct expiration { "4271d23h25m52s"-"8738d3h11m59s" }
-- ct expiration != {33-55};ok
-
-ct helper "ftp";ok
-ct helper "12345678901234567";fail
-
-# BUG: ct l3proto "Layer 3 protocol of the connection"
-# nft add rule ip test input ct l3proto arp
-# <cmdline>:1:35-37: Error: Can t parse symbolic invalid expressions
-
-
-# If table is ip6 or inet or bridge family,, It is failed. I can not test it
-# ct saddr 1.2.3.4;ok
-
-# BUG: ct saddr 192.168.3.4
-# <cmdline>:1:1-43: Error: Could not process rule: Invalid argument
-# add rule ip test input ct saddr 192.168.3.4
-# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-- ct saddr 192.168.3.4;ok
-- ct daddr 192.168.3.4;ok
-
-# BUG: ct protocol tcp
-# <cmdline>:1:1-37: Error: Could not process rule: Invalid argument
-# input ct protocol bgp <cmdline>:1:36-38: Error: Could not resolve protocol name
-# ct protocol tcp;ok
-- ct protocol tcp;ok
-
-- ct proto-src udp;ok
-- ct proto-dst udp;ok
-# BUG: ct proto-src udp and ct proto-dst udp
-# <cmdline>:1:37-39: Error: datatype mismatch, expected invalid, expression has type Internet protocol
-# add rule ip test input ct proto-src udp
-# ~~~~~~~~~~~~ ^^^
-# <cmdline>:1:37-39: Error: datatype mismatch, expected invalid, expression has type Internet protocol
-# add rule ip test input ct proto-dst udp
-# ~~~~~~~~~~~~ ^^^
-
-ct state . ct mark { new . 0x12345678};ok
-ct state . ct mark { new . 0x12345678, new . 0x34127856, established . 0x12785634};ok
-ct direction . ct mark { original . 0x12345678};ok
-ct state . ct mark vmap { new . 0x12345678 : drop};ok