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>
Cc: Kyle Bowman <kbowman@cloudflare.com>,
	Alex Forster <aforster@cloudflare.com>,
	Cloudflare Kernel Team <kernel-team@cloudflare.com>
Subject: [PATCH iptables v2 0/8] extensions: libxt_NFLOG: use nft back-end for iptables-nft
Date: Fri,  1 Oct 2021 18:41:34 +0100	[thread overview]
Message-ID: <20211001174142.1267726-1-jeremy@azazel.net> (raw)

nftables supports 128-character prefixes for nflog whereas legacy
iptables only supports 64 characters.  This patch series converts
iptables-nft to use the nft back-end in order to take advantage of the
longer prefixes.

  * Patches 1-5 implement the conversion and update some related Python
    unit-tests.
  * Patch 6 fixes an minor bug in the output of nflog prefixes.
  * Patch 7 contains a couple of libtool updates.
  * Patch 8 fixes some typo's.

Changes since v1:

  * Patches 1 and 5-8 are new.
  * White-space fixes in patches 2 and 3.
  * Fixes for typo's in commit-messages of patches 2 and 4.
  * Removal of stray `struct xt_nflog_info` allocation from
    `nft_parse_log` in patch 3.
  * Leave commented-out `--nflog-range` test-cases in libxt_NFLOG.t
    with an explanatory comment in patch 4.

Jeremy Sowden (5):
  nft: fix indentation error.
  extensions: libxt_NFLOG: fix `--nflog-prefix` Python test-cases
  extensions: libxt_NFLOG: remove extra space when saving targets with
    prefixes
  build: replace `AM_PROG_LIBTOOL` and `AC_DISABLE_STATIC` with
    `LT_INIT`
  tests: iptables-test: correct misspelt variable

Kyle Bowman (3):
  extensions: libxt_NFLOG: use nft built-in logging instead of xt_NFLOG
  extensions: libxt_NFLOG: don't truncate log prefix on print/save
  extensions: libxt_NFLOG: disable `--nflog-range` Python test-cases

 configure.ac             |  3 +-
 extensions/libxt_NFLOG.c |  8 ++++-
 extensions/libxt_NFLOG.t | 16 ++++-----
 iptables-test.py         | 18 +++++-----
 iptables/nft-shared.c    | 52 ++++++++++++++++++++++++++++
 iptables/nft.c           | 74 ++++++++++++++++++++++++++++------------
 iptables/nft.h           |  1 +
 7 files changed, 131 insertions(+), 41 deletions(-)

-- 
2.33.0


             reply	other threads:[~2021-10-01 17:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 17:41 Jeremy Sowden [this message]
2021-10-01 17:41 ` [PATCH iptables v2 1/8] nft: fix indentation error Jeremy Sowden
2021-10-01 17:41 ` [PATCH iptables v2 2/8] extensions: libxt_NFLOG: use nft built-in logging instead of xt_NFLOG Jeremy Sowden
2022-01-18 12:35   ` Florian Westphal
2021-10-01 17:41 ` [PATCH iptables v2 3/8] extensions: libxt_NFLOG: don't truncate log prefix on print/save Jeremy Sowden
2021-10-01 17:41 ` [PATCH iptables v2 4/8] extensions: libxt_NFLOG: disable `--nflog-range` Python test-cases Jeremy Sowden
2021-10-01 17:41 ` [PATCH iptables v2 5/8] extensions: libxt_NFLOG: fix `--nflog-prefix` " Jeremy Sowden
2021-10-01 17:41 ` [PATCH iptables v2 6/8] extensions: libxt_NFLOG: remove extra space when saving targets with prefixes Jeremy Sowden
2021-10-01 17:41 ` [PATCH iptables v2 7/8] build: replace `AM_PROG_LIBTOOL` and `AC_DISABLE_STATIC` with `LT_INIT` Jeremy Sowden
2021-10-01 17:41 ` [PATCH iptables v2 8/8] tests: iptables-test: correct misspelt variable Jeremy Sowden
2022-01-16 15:05 ` [PATCH iptables v2 0/8] extensions: libxt_NFLOG: use nft back-end for iptables-nft Jeremy Sowden
2022-01-16 19:08   ` Florian Westphal
2022-01-17 10:40     ` Phil Sutter
2022-01-17 21:54       ` Jeremy Sowden
2022-01-18  1:23         ` Pablo Neira Ayuso
2022-01-18  9:33           ` Jeremy Sowden

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=20211001174142.1267726-1-jeremy@azazel.net \
    --to=jeremy@azazel.net \
    --cc=aforster@cloudflare.com \
    --cc=kbowman@cloudflare.com \
    --cc=kernel-team@cloudflare.com \
    --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).