From: Kristian Evensen <kristian.evensen@gmail.com>
To: "Kadlecsik József" <kadlec@blackhole.kfki.hu>
Cc: Netfilter Development Mailing list <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH] ipset: Add wildcard support to net,iface
Date: Thu, 3 Oct 2019 12:02:55 +0200 [thread overview]
Message-ID: <CAKfDRXiMFs5PswdukyWjb60HpoeaUXHG7Hj4gH5Hvx_-0s=-wQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1910022039530.21131@blackhole.kfki.hu>
Hi Jozsef,
On Wed, Oct 2, 2019 at 8:46 PM Kadlecsik József
<kadlec@blackhole.kfki.hu> wrote:
> Sorry for the long delay - I'm still pondering on the syntax.
>
> ip[6]tables uses the "+" notation for prefix matching. So in order to be
> compatible with it, it'd be better to use "ifac+" instead of
> "ifac prefix". The parsing/printing could be solved in the interface
> parser/printer functions internally. What do you think?
No worries about the delay :)
Before submitting the patch, I spent a lot of time thinking about the
syntax since, as you say, ip[6]tables uses "+" to indicate prefix
matching. The first version of the change checked for a "+" at the
end of the interface name, instead of the wildcard flag. However, the
reason I went with the wildcard flag, was that I discovered that "+"
is a valid character in interface names on Linux. One thing we could
do, is to remove any trailing "+" if the wildcard flag is set.
However, I believe such a solution will be a bit redundant, but I have
no strong opinion on how to parse the interface name provided by the
user :)
BR,
Kristian
next prev parent reply other threads:[~2019-10-03 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 10:53 [PATCH] ipset: Add wildcard support to net,iface Kristian Evensen
2019-10-02 18:46 ` Kadlecsik József
2019-10-03 10:02 ` Kristian Evensen [this message]
2019-10-31 9:26 ` Kristian Evensen
2019-10-31 14:14 ` Kadlecsik József
2019-10-31 14:21 ` Kristian Evensen
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='CAKfDRXiMFs5PswdukyWjb60HpoeaUXHG7Hj4gH5Hvx_-0s=-wQ@mail.gmail.com' \
--to=kristian.evensen@gmail.com \
--cc=kadlec@blackhole.kfki.hu \
--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).