From: Phil Sutter <phil@nwl.cc>
To: netfilter-devel@vger.kernel.org
Subject: [iptables PATCH 0/3] Review interface parsing and printing
Date: Fri, 24 Nov 2023 12:28:31 +0100 [thread overview]
Message-ID: <20231124112834.5363-1-phil@nwl.cc> (raw)
Take advantage of the fact that interface name masks are needed only
when submitting a legacy rule to the kernel. Drop all the code dealing
with them and instead introduce a function to call from legacy variants
if needed.
Phil Sutter (3):
xshared: Entirely ignore interface masks when saving rules
xshared: Do not populate interface masks per default
nft: Leave interface masks alone when parsing from kernel
iptables/ip6tables.c | 6 ++-
iptables/iptables.c | 6 ++-
iptables/nft-ipv4.c | 3 +-
iptables/nft-ipv6.c | 3 +-
iptables/nft-ruleparse-arp.c | 5 +-
iptables/nft-ruleparse-bridge.c | 3 +-
iptables/nft-ruleparse-ipv4.c | 5 +-
iptables/nft-ruleparse-ipv6.c | 3 +-
iptables/nft-ruleparse.c | 33 ++++---------
iptables/nft-ruleparse.h | 3 +-
iptables/xshared.c | 83 ++++++++++++++++++---------------
iptables/xshared.h | 8 ++--
12 files changed, 76 insertions(+), 85 deletions(-)
--
2.41.0
next reply other threads:[~2023-11-24 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 11:28 Phil Sutter [this message]
2023-11-24 11:28 ` [iptables PATCH 1/3] xshared: Entirely ignore interface masks when saving rules Phil Sutter
2023-11-24 11:28 ` [iptables PATCH 2/3] xshared: Do not populate interface masks per default Phil Sutter
2023-11-24 11:28 ` [iptables PATCH 3/3] nft: Leave interface masks alone when parsing from kernel Phil Sutter
2023-11-29 1:21 ` [iptables PATCH 0/3] Review interface parsing and printing Phil Sutter
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=20231124112834.5363-1-phil@nwl.cc \
--to=phil@nwl.cc \
--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).