[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164528881161.6364.16449808462091332459.git-patchwork-notify@kernel.org>
Date: Sat, 19 Feb 2022 16:40:11 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Mobashshera Rasool <mobash.rasool.linux@...il.com>
Cc: davem@...emloft.net, oshfuji@...ux-ipv6.org, dsahern@...nel.org,
kuba@...nel.org, netdev@...r.kernel.org,
equinox@...nsourcerouting.org, razor@...ckwall.org,
sharpd@...ulusnetworks.com, mrasool@...are.com
Subject: Re: [PATCH] net: ip6mr: add support for passing full packet on wrong mif
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@...emloft.net>:
On Thu, 17 Feb 2022 07:46:40 +0000 you wrote:
> This patch adds support for MRT6MSG_WRMIFWHOLE which is used to pass
> full packet and real vif id when the incoming interface is wrong.
> While the RP and FHR are setting up state we need to be sending the
> registers encapsulated with all the data inside otherwise we lose it.
> The RP then decapsulates it and forwards it to the interested parties.
> Currently with WRONGMIF we can only be sending empty register packets
> and will lose that data.
> This behaviour can be enabled by using MRT_PIM with
> val == MRT6MSG_WRMIFWHOLE. This doesn't prevent MRT6MSG_WRONGMIF from
> happening, it happens in addition to it, also it is controlled by the same
> throttling parameters as WRONGMIF (i.e. 1 packet per 3 seconds currently).
> Both messages are generated to keep backwards compatibily and avoid
> breaking someone who was enabling MRT_PIM with val == 4, since any
> positive val is accepted and treated the same.
>
> [...]
Here is the summary with links:
- net: ip6mr: add support for passing full packet on wrong mif
https://git.kernel.org/netdev/net-next/c/4b340a5a726d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists