All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Avinash Duduskar <avinash.duduskar@gmail.com>
Cc: netfilter-devel@vger.kernel.org, Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH nft] tests: shell: use an unassigned protocol number in exclusive_start_cond
Date: Thu, 13 Aug 2026 11:43:42 +0200	[thread overview]
Message-ID: <an2RzmRXZBV26Y03@orbyte.nwl.cc> (raw)
In-Reply-To: <20260808013327.2766739-1-avinash.duduskar@gmail.com>

Hi Avinash,

On Sat, Aug 08, 2026 at 07:03:27AM +0530, Avinash Duduskar wrote:
> nft renders nexthdr through getprotobynumber(), so the dump records whichever
> name the host's /etc/protocols gives for the value. 0 is "ip" on Debian, which
> carries the legacy alias ahead of hopopt, and "hopopt" where /etc/protocols is
> generated from the IANA registry, which assigns only HOPOPT. The test fails
> there, and the dump cannot be reloaded either, because getprotobyname("ip")
> finds nothing.
> 
> 200 is unassigned in both, so it prints numerically everywhere. 255 would not
> do: Arch's iana-etc names it "reserved".

Instead of playing whack-a-mole, we should pass '--numeric-proto
--stateless' to nft calls just like py test suite does. Let me submit
patches for shell test suite so we have evidence for a discussion.

Cheers, Phil

  reply	other threads:[~2026-08-13  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-08  1:33 [PATCH nft] tests: shell: use an unassigned protocol number in exclusive_start_cond Avinash Duduskar
2026-08-13  9:43 ` Phil Sutter [this message]
2026-08-14 21:10   ` Avinash Duduskar

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=an2RzmRXZBV26Y03@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --cc=avinash.duduskar@gmail.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.