From: Christoph Anton Mitterer <calestyo@scientia.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: bug: nft -n still shows "resolved" values for iif and oif
Date: Thu, 25 Sep 2025 22:44:06 +0200 [thread overview]
Message-ID: <a14a19376e165796b8b4989fec1739a830c4b2e5.camel@scientia.org> (raw)
In-Reply-To: <aNVxqaP7iZpeMh6S@strlen.de>
On Thu, 2025-09-25 at 18:45 +0200, Florian Westphal wrote:
> Sure, only when renamed. When you remove it raw value is shown
> and it won't match anymore.
Still, when explicitly using --numeric, which one can expect to show
the real values that are matched, and it still shows the string,...
then I guess it's easy for people to wrongly expect that it would
actually match on the name.
> Sure but why do you use iif with a interface that gets removed in
> between?
Well, *I* don't, but given the number of examples floating around that
use iif/oif I guess it's safe to assume that many users might not
realise.
And I'd have argued that the whole point of a --numeric is to show the
real values, that are actually used for matching.
Except that for values where the names are statically defined, I'd have
argued one could use a double -n to make them print the real numbers.
Aynway... not a big deal.
Cheers,
Chris.
prev parent reply other threads:[~2025-09-25 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 21:48 bug: nft -n still shows "resolved" values for iif and oif Christoph Anton Mitterer
2025-09-25 12:36 ` Fernando Fernandez Mancera
2025-09-25 14:07 ` Pablo Neira Ayuso
2025-09-26 10:27 ` Fernando Fernandez Mancera
2025-09-25 15:48 ` Christoph Anton Mitterer
2025-09-25 14:42 ` Florian Westphal
2025-09-25 15:53 ` Christoph Anton Mitterer
2025-09-25 16:45 ` Florian Westphal
2025-09-25 20:44 ` Christoph Anton Mitterer [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=a14a19376e165796b8b4989fec1739a830c4b2e5.camel@scientia.org \
--to=calestyo@scientia.org \
--cc=fw@strlen.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).