Re: bug: nft -n still shows "resolved" values for iif and oif

[Christoph Anton Mitterer <calestyo@scientia.org>]

On Thu, 2025-09-25 at 14:36 +0200, Fernando Fernandez Mancera wrote:
> 2. Introduce a new "--numeric-interface" which prevents resolving iif
> or 
> oif.

What IMO would be most helpful for users is an option, which for all
values simply causes the "real" value to be printed.

With "real" I mean:
- if e.g. an ip daddr matches on 1.1.1.1, then print 1.1.1.1
- if there were an ip domainname where netfilter would resolve, the
  that option should print the hostname
- if using iifname, the actual matched value is the string, so print
  that
- if using iif or oif, the actual matched value is the ID, so print
  that, in particular as (perhaps with the exception of lo), e.g. eth0
  isn't per definition ID 2 or whatever


For things like ICMP Type codes, IP protocol numbers, port numbers...
things are different to e.g. the iface ID.
For them, e.g. type 0 is always guaranteed to be icmp echo request and
22 is always port SSH.


So it could IMO be handy to have an option which gives the above
("real") but still uses non-numeric values for things where the
number<->string is fixed, and if one uses the option e.g. twice, then
even those are printed with their numeric values.


Cheers,
Chris.