From: patchwork-bot+netdevbpf@kernel.org
To: Thomas Winter <Thomas.Winter@alliedtelesis.co.nz>
Cc: davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
pabeni@redhat.com, edumazet@google.com, kuba@kernel.org,
a@unstable.cc, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] ip/ip6_gre: Fix GRE tunnels not generating IPv6 link local addresses
Date: Thu, 02 Feb 2023 04:00:17 +0000 [thread overview]
Message-ID: <167531041794.2562.11007852335746128637.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230131034646.237671-1-Thomas.Winter@alliedtelesis.co.nz>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 31 Jan 2023 16:46:44 +1300 you wrote:
> For our point-to-point GRE tunnels, they have IN6_ADDR_GEN_MODE_NONE
> when they are created then we set IN6_ADDR_GEN_MODE_EUI64 when they
> come up to generate the IPv6 link local address for the interface.
> Recently we found that they were no longer generating IPv6 addresses.
>
> Also, non-point-to-point tunnels were not generating any IPv6 link
> local address and instead generating an IPv6 compat address,
> breaking IPv6 communication on the tunnel.
>
> [...]
Here is the summary with links:
- [v5,1/2] ip/ip6_gre: Fix changing addr gen mode not generating IPv6 link local address
https://git.kernel.org/netdev/net/c/23ca0c2c9340
- [v5,2/2] ip/ip6_gre: Fix non-point-to-point tunnel not generating IPv6 link local address
https://git.kernel.org/netdev/net/c/30e2291f61f9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-02 4:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 3:46 Thomas Winter
2023-01-31 3:46 ` [PATCH v5 1/2] ip/ip6_gre: Fix changing addr gen mode not generating IPv6 link local address Thomas Winter
2023-01-31 16:03 ` David Ahern
2023-01-31 3:46 ` [PATCH v5 2/2] ip/ip6_gre: Fix non-point-to-point tunnel " Thomas Winter
2023-02-02 4:00 ` patchwork-bot+netdevbpf [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=167531041794.2562.11007852335746128637.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Thomas.Winter@alliedtelesis.co.nz \
--cc=a@unstable.cc \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.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
Powered by JetHome