netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Davidson <davidson.brian@gmail.com>
To: netfilter@vger.kernel.org
Subject: ip6 dscp fails map lookup
Date: Fri, 3 Nov 2023 12:18:59 -0400	[thread overview]
Message-ID: <CAOoaxdEpJDAQMYxRCC6rUVc=sMY=YXxF42LSeDvMQUPC5sahLA@mail.gmail.com> (raw)

Using 'ip6 dscp' in a map lookup does not give expected results. It
seems to always match the zero value (cs0). It appears in the first
rule that the byteorder is not being converted between the two bitwise
operations, which is what happens when using ip6 dscp directly in the
second rule.

# nft -f - <<EOF
add table ip6 t
add chain ip6 t c
add map ip6 t mapv6 { typeof ip6 dscp : meta mark; }
EOF

# nft -d netlink add rule ip6 t c meta mark set ip6 dscp map @mapv6
ip6 t c
  [ payload load 2b @ network header + 0 => reg 1 ]
  [ bitwise reg 1 = ( reg 1 & 0x0000c00f ) ^ 0x00000000 ]
  [ bitwise reg 1 = ( reg 1 >> 0x00000006 ) ]
  [ lookup reg 1 set mapv6 dreg 1 ]
  [ meta set mark with reg 1 ]

# nft -d netlink add rule ip6 t c meta mark set ip6 dscp
ip6 t c
  [ payload load 2b @ network header + 0 => reg 1 ]
  [ bitwise reg 1 = ( reg 1 & 0x0000c00f ) ^ 0x00000000 ]
  [ byteorder reg 1 = ntoh(reg 1, 2, 2) ]
  [ bitwise reg 1 = ( reg 1 >> 0x00000006 ) ]
  [ meta set mark with reg 1 ]

             reply	other threads:[~2023-11-03 16:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 16:18 Brian Davidson [this message]
2023-11-03 19:37 ` ip6 dscp fails map lookup Florian Westphal
2023-11-03 21:59   ` Florian Westphal
2023-11-05 17:15     ` Pablo Neira Ayuso
2023-11-05 17:41       ` Florian Westphal
2023-11-05 17:58         ` Pablo Neira Ayuso
2023-11-05 21:33         ` Pablo Neira Ayuso

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='CAOoaxdEpJDAQMYxRCC6rUVc=sMY=YXxF42LSeDvMQUPC5sahLA@mail.gmail.com' \
    --to=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).