netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nft 0/3] nftables: add support for wildcard interfaces
Date: Fri, 29 Apr 2022 20:32:36 +0200	[thread overview]
Message-ID: <20220429183239.5569-1-fw@strlen.de> (raw)

First patch is needed so kernel doesn't think end is before start,
second patch allows to dump "x .foo*" correctly, without this
nft tries to represent the start/end "name" with a range.
This doesn't work well because end range uses \ff padding.

Patch 3 adds tests.

Florian Westphal (3):
  netlink: swap byteorder for host-endian concat data
  segtree: add pretty-print support for wildcard strings in concatenated
    sets
  sets_with_ifnames: add test case for concatenated range

 src/netlink.c                                 |  4 +
 src/segtree.c                                 | 38 +++++++-
 .../sets/dumps/sets_with_ifnames.nft          | 25 ++++-
 tests/shell/testcases/sets/sets_with_ifnames  | 93 ++++++++++++++-----
 4 files changed, 134 insertions(+), 26 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-04-29 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 18:32 Florian Westphal [this message]
2022-04-29 18:32 ` [PATCH nft 1/3] netlink: swap byteorder for host-endian concat data Florian Westphal
2022-04-29 18:32 ` [PATCH nft 2/3] segtree: add pretty-print support for wildcard strings in concatenated sets Florian Westphal
2022-04-29 18:32 ` [PATCH nft 3/3] sets_with_ifnames: add test case for concatenated range Florian Westphal
2022-05-02 18:58 ` [PATCH nft 0/3] nftables: add support for wildcard interfaces Pablo Neira Ayuso

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=20220429183239.5569-1-fw@strlen.de \
    --to=fw@strlen.de \
    --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).