From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Felix Kluge <f.kluge@agdsn.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nft bug: Deleting map elements with intervals
Date: Sun, 26 Feb 2017 21:09:58 +0100 [thread overview]
Message-ID: <20170226200958.GA1827@salvia> (raw)
In-Reply-To: <20170226163855.v56ljeaelgqypaeq@wendy>
On Sun, Feb 26, 2017 at 05:38:55PM +0100, Felix Kluge wrote:
> Hello,
>
> we're currently trying to use a vertict map to jump to other chains. The
> key of the map is a subnet.
>
> table ip filter {
> map cgn_map {
> type ipv4_addr : verdict
> flags interval
> elements = {
> 100.64.2.0/24 : goto chain-100-64-2-0}
> }
> }
>
>
> Adding new elements to the map works well:
>
> nft add element filter cgn_map { 100.64.3.0/24 : goto ratelimit-100-64-3-0}
>
>
> However, deleting elements from the map does not work:
>
> nft delete element filter cgn_map 100.64.2.0/24
> <cmdline>:1:36-45: Error: syntax error, unexpected string, expecting '{' or '$'
Parens are missing, this should be:
nft delete element filter cgn_map { 100.64.2.0/24 }
Thanks.
prev parent reply other threads:[~2017-02-26 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 16:38 nft bug: Deleting map elements with intervals Felix Kluge
2017-02-26 20:09 ` Pablo Neira Ayuso [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=20170226200958.GA1827@salvia \
--to=pablo@netfilter.org \
--cc=f.kluge@agdsn.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 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.