From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Leon Merten Lohse <leon@green-side.de>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables: named set for ipv4 networks
Date: Thu, 27 Oct 2016 21:23:38 +0200 [thread overview]
Message-ID: <20161027192338.GA1570@salvia> (raw)
In-Reply-To: <20161023213822.16337e5c@doomgiver>
On Sun, Oct 23, 2016 at 09:38:22PM +0200, Leon Merten Lohse wrote:
> Hi,
>
> is there a way to migrate a hash:net type ipset to nftables?
> We use this to implement a blacklist where we block a large number of
> networks.
>
> I tried using a type ipv4_addr named set as follows:
>
> flush ruleset
> table inet filter {
> set blacklist_v4 { type ipv4_addr; }
> }
> add element inet filter blacklist_v4 { 10.0.0.0/8 }
>
> However, this results in:
> Error: Set member cannot be prefix, missing interval flag on declaration
> add element inet filter blacklist_v4 { 10.0.0.0/8 }
> ^^^^^^^^^^
> Is ipv4_addr the wrong type in this case? I could not find any
> documentation on it.
> Using networks in anonymous sets seems to work flawlessly.
Missing "flags interval;" here, so this should be:
table inet filter {
set blacklist_v4 { type ipv4_addr; flags interval; }
}
With named sets, you have to specify this flag since the kernel uses
to select what is the best data structure uses to represent what you
need.
next prev parent reply other threads:[~2016-10-27 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 19:38 nftables: named set for ipv4 networks Leon Merten Lohse
2016-10-27 19:23 ` Pablo Neira Ayuso [this message]
2016-10-27 21:41 ` Leon Merten Lohse
2016-10-28 8:04 ` Pablo Neira Ayuso
2016-10-28 14:23 ` Leon Merten Lohse
2016-11-02 10:30 ` Leon Merten Lohse
2016-11-03 11:29 ` Arturo Borrero Gonzalez
2016-11-29 23:00 ` Leon Merten Lohse
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=20161027192338.GA1570@salvia \
--to=pablo@netfilter.org \
--cc=leon@green-side.de \
--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.