netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "William N." <netfilter@riseup.net>
To: netfilter@vger.kernel.org
Subject: Re: nftables: How to match ICMPv6 subtype in a rule?
Date: Sun, 31 Mar 2024 17:02:59 -0000	[thread overview]
Message-ID: <20240331170259.068a0db3@localhost> (raw)
In-Reply-To: <f1e198cf-949e-4dbe-becb-25d2ee4c2950@app.fastmail.com>

Thanks for clarifying.

I actually found the magic word "code" after posting here but I still
wanted to wait for a reply. Yours explained it perfectly. I suppose I
have been confused by reading too much from different sources :)

On Sun, 31 Mar 2024 07:33:42 +0100 Kerin Millar wrote:

> However, there are some errors in the manual. [...]

Have those been reported anywhere?

> icmpv6 code <icmpv6_code> # where <icmpv6_code> is any valid ICMPV6
> CODE value

Having such possibility is interesting, as the integer code has
different meaning depending on the type, i.e. it has no meaning per se
and it looks strange to filter based on it only. I thought they must go
"hand in hand" but obviously not. I wonder what purpose such filtering
may serve.

In that sense, the output of:

> # nft describe icmpv6_code

is somewhat confusing (e.g. compare type 1 and type 3 or 4 in RFC 4443).

  reply	other threads:[~2024-03-31 17:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30 19:41 nftables: How to match ICMPv6 subtype in a rule? William N.
2024-03-31  6:33 ` Kerin Millar
2024-03-31 17:02   ` William N. [this message]
2024-03-31 18:34     ` Kerin Millar
2024-04-01 17:19       ` William N.
2024-04-01 22:59       ` Pablo Neira Ayuso
2024-04-02  7:29         ` William N.
2024-04-02 10:06           ` Pablo Neira Ayuso
2024-04-02 13:24             ` William N.

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=20240331170259.068a0db3@localhost \
    --to=netfilter@riseup.net \
    --cc=netfilter@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).