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: Fri, 28 Oct 2016 10:04:19 +0200 [thread overview]
Message-ID: <20161028080419.GB1553@salvia> (raw)
In-Reply-To: <20161027234152.2c94a832@doomgiver>
On Thu, Oct 27, 2016 at 11:41:52PM +0200, Leon Merten Lohse wrote:
> (repost to list. sorry for the duplicate)
>
> Thank you, Pablo!
> Unfortunately this results in a segfault for me. I was able to boil the
> ruleset down to a minimal example that segfaults.
>
> # nft -f segfault.ruleset
> Segmentation fault
>
> Even if I made a severe error, it should not segfault, right? ..
>
> Versions of nftables and kernel are as in my previous emails.
>
> Best
> Leon
>
> ---
>
> # segfault.ruleset
>
> flush ruleset
>
> table inet filter {
> # blocked networks
> set blacklist_v4 { type ipv4_addr; flags interval; }
> }
>
> # this would be included from a generated file
> add element inet filter blacklist_v4 {
> 192.168.0.1/24,
> }
This is working here.
Your nft version is probably missing this patch:
http://git.netfilter.org/nftables/commit/?id=24c9e993eeff0ed41875aa7efef5dd69db4eb537
Could you please grab a nftables git.netfilter.org clone and confirm
this works for you?
We're planning for the nft 0.7 release, so it would be good if you can
help us confirm that the problem is already gone.
Thanks.
next prev parent reply other threads:[~2016-10-28 8:04 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
2016-10-27 21:41 ` Leon Merten Lohse
2016-10-28 8:04 ` Pablo Neira Ayuso [this message]
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=20161028080419.GB1553@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.