From: Florian Westphal <fw@strlen.de>
To: netfilter-devel@vger.kernel.org
Cc: ian.kumlien@gmail.com
Subject: Re: [Bug 1145] nft 0.7: expression.c:966: range_expr_value_low: Assertion '0' failed.
Date: Mon, 15 May 2017 14:03:57 +0200 [thread overview]
Message-ID: <20170515120357.GA32767@breakpoint.cc> (raw)
In-Reply-To: <bug-1145-20-O7t1kbwESB@https.bugzilla.netfilter.org/>
bugzilla-daemon@netfilter.org <bugzilla-daemon@netfilter.org> wrote:
[ Switching to email ]
> https://bugzilla.netfilter.org/show_bug.cgi?id=1145
>
> --- Comment #1 from Ian Kumlien <ian.kumlien@gmail.com> ---
> Is there anything obvious that i'm doing wrong? Is there something else i could
> try?
This boils down to nested sets:
define dnat_host = 10.1.2.3
define dnat_ports = { 1234-1567 }
define port_allow = {
53, # dns
$dnat_ports, # dnat
}
define port_allow_tcp = {
80,
443,
$port_allow
}
define port_allow_udp = {
67, 68, # dhcp
123, 1027, # ntp
$port_allow
}
... which we don't support at the moment.
So, should we
a). expand/'inline' the sets?
(i.e. port_allow_tcp would contain
1234-1567, 53, 80, 443)
b) support lookups within lookups?
This would be needed to support non-anonymous sets within sets.
or
c) never support this? This would probably need some work on parser
to be able to provide a clean error message rather than BUG() ...
Opinions?
next parent reply other threads:[~2017-05-15 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1145-20@https.bugzilla.netfilter.org/>
[not found] ` <bug-1145-20-O7t1kbwESB@https.bugzilla.netfilter.org/>
2017-05-15 12:03 ` Florian Westphal [this message]
2017-05-16 11:34 ` [Bug 1145] nft 0.7: expression.c:966: range_expr_value_low: Assertion '0' failed Phil Sutter
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=20170515120357.GA32767@breakpoint.cc \
--to=fw@strlen.de \
--cc=ian.kumlien@gmail.com \
--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).