Linux Netfilter development
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, Yi Chen <yiche@redhat.com>
Subject: Re: [PATCH nf] netfilter: Use flowlabel flow key when re-routing mangled packets
Date: Tue, 11 Jun 2024 18:44:44 +0200	[thread overview]
Message-ID: <Zmh-_F9bJJOrnkbY@calendula> (raw)
In-Reply-To: <20240606102334.5521-1-fw@strlen.de>

On Thu, Jun 06, 2024 at 12:23:31PM +0200, Florian Westphal wrote:
> 'ip6 dscp set $v' in an nftables outpute route chain has no effect.
> While nftables does detect the dscp change and calls the reroute hook.
> But ip6_route_me_harder never sets the dscp/flowlabel:
> flowlabel/dsfield routing rules are ignored and no reroute takes place.
> 
> Thanks to Yi Chen for an excellent reproducer script that I used
> to validate this change.

Applied to nf.git, thanks Florian

      reply	other threads:[~2024-06-11 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 10:23 [PATCH nf] netfilter: Use flowlabel flow key when re-routing mangled packets Florian Westphal
2024-06-11 16:44 ` 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=Zmh-_F9bJJOrnkbY@calendula \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=yiche@redhat.com \
    /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