netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Sowden <jeremy@azazel.net>
To: Netfilter Devel <netfilter-devel@vger.kernel.org>
Subject: [iptables PATCH 0/4] Re-enable NFLOG tests
Date: Sat, 12 Feb 2022 16:58:28 +0000	[thread overview]
Message-ID: <20220212165832.2452695-1-jeremy@azazel.net> (raw)

Some of the NFLOG tests were disabled when iptables-nft was changed to
use nft's nflog implementation, because nft doesn't support
`--nflog-range`.  This patch-set builds on Phil's recent work to support
different test results for -legacy and -nft in order to re-enable those
tests.

* Patch 1 renames a variable.
* Patches 2 & 3 add support for a new test result where the iptables
  command succeeds, but dumping the rule does not give the expected
  output.
* Patch 4 re-enables the tests.

Jeremy Sowden (4):
  tests: iptables-test: rename variable
  tests: add `NOMATCH` test result
  tests: support explicit variant test result
  tests: NFLOG: enable `--nflog-range` tests

 extensions/libxt_NFLOG.t | 12 +++----
 iptables-test.py         | 72 ++++++++++++++++++++++++++--------------
 2 files changed, 53 insertions(+), 31 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-02-12 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12 16:58 Jeremy Sowden [this message]
2022-02-12 16:58 ` [iptables PATCH 1/4] tests: iptables-test: rename variable Jeremy Sowden
2022-02-12 16:58 ` [iptables PATCH 2/4] tests: add `NOMATCH` test result Jeremy Sowden
2022-02-14 10:01   ` Phil Sutter
2022-02-20 13:10     ` Jeremy Sowden
2022-02-22 10:09       ` Phil Sutter
2022-02-12 16:58 ` [iptables PATCH 3/4] tests: support explicit variant " Jeremy Sowden
2022-02-12 16:58 ` [iptables PATCH 4/4] tests: NFLOG: enable `--nflog-range` tests Jeremy Sowden
2022-02-13 21:28 ` [iptables PATCH 0/4] Re-enable NFLOG tests Florian Westphal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220212165832.2452695-1-jeremy@azazel.net \
    --to=jeremy@azazel.net \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).