From: David Ahern <dsahern@kernel.org>
To: Martin Willi <martin@strongswan.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH nf v2 2/2] netfilter: Use l3mdev flow key when re-routing mangled packets
Date: Tue, 19 Apr 2022 14:06:23 -0600 [thread overview]
Message-ID: <1941bfc8-fa2a-16f6-a70b-df3b7d963dd7@kernel.org> (raw)
In-Reply-To: <20220419134701.153090-3-martin@strongswan.org>
On 4/19/22 7:47 AM, Martin Willi wrote:
> Commit 40867d74c374 ("net: Add l3mdev index to flow struct and avoid oif
> reset for port devices") introduces a flow key specific for layer 3
> domains, such as a VRF master device. This allows for explicit VRF domain
> selection instead of abusing the oif flow key.
>
> Update ip[6]_route_me_harder() to make use of that new key when re-routing
> mangled packets within VRFs instead of setting the flow oif, making it
> consistent with other users.
>
> Signed-off-by: Martin Willi <martin@strongswan.org>
> ---
> net/ipv4/netfilter.c | 3 +--
> net/ipv6/netfilter.c | 3 +--
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
>
This one will go to -next
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2022-04-19 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 13:46 [PATCH nf v2 0/2] netfilter: Fix/update mangled packet re-routing within VRF domains Martin Willi
2022-04-19 13:47 ` [PATCH nf v2 1/2] netfilter: Update ip6_route_me_harder to consider L3 domain Martin Willi
2022-04-19 20:05 ` David Ahern
2022-04-25 9:09 ` Pablo Neira Ayuso
2022-04-19 13:47 ` [PATCH nf v2 2/2] netfilter: Use l3mdev flow key when re-routing mangled packets Martin Willi
2022-04-19 20:06 ` David Ahern [this message]
2022-05-16 11:03 ` 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=1941bfc8-fa2a-16f6-a70b-df3b7d963dd7@kernel.org \
--to=dsahern@kernel.org \
--cc=fw@strlen.de \
--cc=martin@strongswan.org \
--cc=netdev@vger.kernel.org \
--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 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).