From: Leon Merten Lohse <leon@green-side.de>
To: Netfilter Users Mailing list <netfilter@vger.kernel.org>
Subject: Re: nftables: named set for ipv4 networks
Date: Wed, 30 Nov 2016 00:00:11 +0100 [thread overview]
Message-ID: <20161130000011.0a751e9a@doomgiver> (raw)
In-Reply-To: <CAOkSjBjWmNZFHnYu5B=FcM1qT3sUWBBq+=9Kk8WsEzu6F0JV6Q@mail.gmail.com>
Is there a fix in sight for this? Can I be of assistance somehow?
Best
Leon
On Thu, 3 Nov 2016 12:29:28 +0100
Arturo Borrero Gonzalez <arturo@debian.org> wrote:
> On 2 November 2016 at 11:30, Leon Merten Lohse <leon@green-side.de>
> wrote:
> > I would really appreciate if someone could comment on this.
> >
> > The problem is that nft complains about overlapping intervals in the
> > set, if I load the following ruleset twice.
> > This occurs even though there is a `flush ruleset' directive at the
> > beginning of the ruleset. As far as I understand it, all sets
> > should be empty after that.
> > Calling `nft flush ruleset' beforehand works around this but is no
> > longer atomic.
> >
>
> Yes, this is probably some bug in the nft cache.
>
> Will send a testcase so we don't forget about fixing this.
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-11-29 23:00 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
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 [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=20161130000011.0a751e9a@doomgiver \
--to=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.