From: Florian Westphal <fw@strlen.de>
To: Matt Zagrabelny <mzagrabe@d.umn.edu>
Cc: netfilter <netfilter@vger.kernel.org>
Subject: Re: nft named set address types
Date: Tue, 2 Nov 2021 20:53:52 +0100 [thread overview]
Message-ID: <20211102195352.GA11415@breakpoint.cc> (raw)
In-Reply-To: <CAOLfK3UFmzPfaqZbB5z6kvRuvpmHrFptbf1_LLBfJdPPzVHwqQ@mail.gmail.com>
Matt Zagrabelny <mzagrabe@d.umn.edu> wrote:
> I'd like to use the "inet" address family in a named set. I see nft
> supports the following address families [AF] (among others):
>
> ip IPv4 address family.
>
> ip6 IPv6 address family.
>
> inet Internet (IPv4/IPv6) address
> family.
>
> However, looking at the named sets, I do not see the "inet" AF:
>
> type string: ipv4_addr, ipv6_addr, ether_addr, inet_proto, inet_service, mark
>
> Are there plans to add "inet_addr" AF to the types of named sets?
No.
> Any feedback about combined ipv4 and ipv6 address families in named
> sets? or why an inet family does not exist for named sets?
There is no ip family either, only data types, and all must have a fixed
length.
nft describe ip saddr
prev parent reply other threads:[~2021-11-02 19:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 20:46 nft named set address types Matt Zagrabelny
2021-11-02 19:39 ` Matt Zagrabelny
2021-11-02 20:23 ` Pablo Neira Ayuso
2021-11-02 20:56 ` Matt Zagrabelny
2021-11-15 17:40 ` Matt Zagrabelny
2021-11-15 17:59 ` Eugene Crosser
2021-11-15 19:00 ` Kerin Millar
2021-11-15 19:47 ` Pablo Neira Ayuso
2021-11-16 2:20 ` Pablo Neira Ayuso
2021-11-16 2:55 ` Matt Zagrabelny
2021-11-16 8:35 ` Pablo Neira Ayuso
2021-11-02 19:53 ` Florian Westphal [this message]
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=20211102195352.GA11415@breakpoint.cc \
--to=fw@strlen.de \
--cc=mzagrabe@d.umn.edu \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.