path: root/tests/py/ip/ct.t.payload
Commit message (Collapse)AuthorAgeFilesLines
* tests: ct: adjust test case commandsFlorian Westphal2017-09-291-8/+8
| | | | | | use 'ip saddr', 'ip6 saddr', etc. Signed-off-by: Florian Westphal <>
* src: support ct l3proto/protocol without direction syntaxLiping Zhang2016-10-171-4/+4
| | | | | | | | | | | | | | | Acctually, ct l3proto and ct protocol are unrelated to direction, so it's unnecessary that we must specify dir if we want to use them. Now add support that we can match ct l3proto/protocol without direction: # nft add rule filter input ct l3proto ipv4 # nft add rule filter output ct protocol 17 Note: existing syntax is still preserved, so "ct reply l3proto ipv6" is still fine. Signed-off-by: Liping Zhang <> Signed-off-by: Pablo Neira Ayuso <>
* nft: swap key and direction in ct_dir syntaxFlorian Westphal2016-01-071-11/+11
| | | | | | | | | | | | | | | old: ct saddr original new: ct original saddr The advantage is that this allows to add ct keys where direction is optional without creating ambiguities in the parser. So we can have ct packets gt 42 ct original packets gt 42 Signed-off-by: Florian Westphal <> Acked-by: Pablo Neira Ayuso <>
* tests: add ct tests for ip familyFlorian Westphal2016-01-041-0/+62
Cannot check e.g. saddr for for 'any' protocol, nft needs to expect arguments of a specific address type. So e.g. when using 'inet' we need to add a rule that makes the expected family explicit, e.g. 'meta nfproto ipv4'. Signed-off-by: Florian Westphal <>