netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Brian Davidson <davidson.brian@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables 1.0.8 showing invalid type for ip dscp
Date: Wed, 19 Jul 2023 02:16:07 +0200	[thread overview]
Message-ID: <ZLcrR3/BdjsvDQIF@calendula> (raw)
In-Reply-To: <CAOoaxdHd1RHx8o4uWFtMAVV0D59uNv7_JApfC1S6uoUGrsf_2A@mail.gmail.com>

Hi,

Thanks for reporting.

On Tue, Jul 18, 2023 at 11:31:38AM -0400, Brian Davidson wrote:
> The following ruleset setting ct mark from ip dscp does not display
> the right-hand expression 'ip dscp' correctly when listing the
> ruleset.

This patch fixes this issue:

https://patchwork.ozlabs.org/project/netfilter-devel/patch/20230719001444.154070-1-pablo@netfilter.org/

> It instead displays '@nh,8,8 & 0xfc [invalid type]'.  'ip6 dscp' looks normal.
> 
> table inet x {
>         chain y {
>                 type filter hook postrouting priority mangle + 1; policy accept;
>                 ct mark set ip dscp | 0x40 counter
>                 ct mark set ip6 dscp | 0x40 counter
>         }
> }
> 
> # nft list table inet x
> table inet x {
>         chain y {
>                 type filter hook postrouting priority mangle + 1; policy accept;
>                 meta nfproto ipv4 ct mark set @nh,8,8 & 0xfc [invalid
> type] | 0x40 counter packets 3584 bytes 575402
>                 ct mark set ip6 dscp | 0x40 counter packets 755 bytes 255731
>         }
> }

      reply	other threads:[~2023-07-19  0:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 15:31 nftables 1.0.8 showing invalid type for ip dscp Brian Davidson
2023-07-19  0:16 ` Pablo Neira Ayuso [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=ZLcrR3/BdjsvDQIF@calendula \
    --to=pablo@netfilter.org \
    --cc=davidson.brian@gmail.com \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).