From: Florian Zumbiehl <florz@florz.de>
To: netfilter-devel@vger.kernel.org
Subject: [nftables] bug: set output inconsistent syntax and missing information
Date: Sun, 5 Jan 2020 02:21:46 +0100 [thread overview]
Message-ID: <20200105012145.GF3854@florz.florz.de> (raw)
Hi,
... and then I stumbled upon yet another bug:
| # nft 'table ip foobartest { set s { type ipv4_addr; flags interval,timeout; elements={ 0.0.0.0/0 timeout 1d comment foo }; }; }'
| # nft list set foobartest s
| table ip foobartest {
| set s {
| type ipv4_addr
| flags interval,timeout
| elements = { 0.0.0.0-255.255.255.255 }
| }
| }
Any "trailing" ranges in a set that reach to the end of the address space are
(a) output as ranges rather than prefixes and (b) lack the comment and timeout
info.
My guess would be that that is due to the trailing special case at the end of
interval_map_decompose()?
Regards, Florian
reply other threads:[~2020-01-05 1:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200105012145.GF3854@florz.florz.de \
--to=florz@florz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).