From: patchwork-bot+netdevbpf@kernel•org
To: Mobashshera Rasool <mobash.rasool.linux@gmail•com>
Cc: davem@davemloft•net, oshfuji@linux-ipv6•org, dsahern@kernel•org,
kuba@kernel•org, netdev@vger•kernel.org,
equinox@opensourcerouting•org, razor@blackwall•org,
sharpd@cumulusnetworks•com, mrasool@vmware•com
Subject: Re: [PATCH] net: ip6mr: add support for passing full packet on wrong mif
Date: Sat, 19 Feb 2022 16:40:11 +0000 [thread overview]
Message-ID: <164528881161.6364.16449808462091332459.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220217074640.4472-1-mobash.rasool.linux@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft•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
next prev parent reply other threads:[~2022-02-19 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 7:46 [PATCH] net: ip6mr: add support for passing full packet on wrong mif Mobashshera Rasool
2022-02-19 16:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-16 17:53 Mobashshera Rasool
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=164528881161.6364.16449808462091332459.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=equinox@opensourcerouting$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=mobash.rasool.linux@gmail$(echo .)com \
--cc=mrasool@vmware$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=oshfuji@linux-ipv6$(echo .)org \
--cc=razor@blackwall$(echo .)org \
--cc=sharpd@cumulusnetworks$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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