netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: hanhuihui <hanhuihui5@huawei.com>
To: <idosch@idosch.org>
Cc: <dsahern@kernel.org>, <hanhuihui5@huawei.com>, <kuba@kernel.org>,
	<netdev@vger.kernel.org>
Subject: Re: VRF Routing Rule Matching Issue: oif Rules Not Working After Commit 40867d74c374
Date: Sat, 12 Apr 2025 21:17:43 +0800	[thread overview]
Message-ID: <20250412131743.14507-1-hanhuihui5@huawei.com> (raw)
In-Reply-To: <Z_V--XONvQZaFCJ8@shredder>

On Tue, 8 Apr 2025 22:54:33 +0300 Ido Schimmel wrote:
>Before 40867d74c374 you couldn't match with FIB rules on oif/iif being a
>VRF slave because these fields in the flow structure were reset to the
>index of the VRF device in l3mdev_update_flow().
>
>I will try to check if we can interpret FIB rules with "oif" / "iif"
>pointing to a VRF as matching on "fl->flowi_l3mdev" rather than
>"fl->flowi_oif" / "fl->flowi_iif".
Thank you for your reply. Followed by a simple patch to restore the 
previous behavior, hopefully enlightening you.

  reply	other threads:[~2025-04-12 13:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03  1:58 VRF Routing Rule Matching Issue: oif Rules Not Working After Commit 40867d74c374 hanhuihui
2025-04-07  8:29 ` Ido Schimmel
2025-04-08 16:17   ` hanhuihui
2025-04-08 16:49     ` David Ahern
2025-04-08 19:54     ` Ido Schimmel
2025-04-12 13:17       ` hanhuihui [this message]
2025-04-12 13:19       ` [PATCH] resume oif rule match l3mdev in fib_lookup hanhuihui
2025-04-12 23:25         ` Jakub Kicinski
2025-04-14  7:17         ` Ido Schimmel
2025-04-14 17:24           ` Ido Schimmel
2025-04-15 14:11             ` hanhuihui

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=20250412131743.14507-1-hanhuihui5@huawei.com \
    --to=hanhuihui5@huawei.com \
    --cc=dsahern@kernel.org \
    --cc=idosch@idosch.org \
    --cc=kuba@kernel.org \
    --cc=netdev@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).