From: patchwork-bot+netdevbpf@kernel.org
To: Gergely Risko <gergely.risko@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, stable@vger.kernel.org
Subject: Re: [PATCH net] ipv6: fix reachability confirmation with proxy_ndp
Date: Mon, 23 Jan 2023 11:20:17 +0000 [thread overview]
Message-ID: <167447281736.14272.18315324318489774078.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230119134041.951006-1-gergely.risko@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 19 Jan 2023 14:40:41 +0100 you wrote:
> When proxying IPv6 NDP requests, the adverts to the initial multicast
> solicits are correct and working. On the other hand, when later a
> reachability confirmation is requested (on unicast), no reply is sent.
>
> This causes the neighbor entry expiring on the sending node, which is
> mostly a non-issue, as a new multicast request is sent. There are
> routers, where the multicast requests are intentionally delayed, and in
> these environments the current implementation causes periodic packet
> loss for the proxied endpoints.
>
> [...]
Here is the summary with links:
- [net] ipv6: fix reachability confirmation with proxy_ndp
https://git.kernel.org/netdev/net/c/9f535c870e49
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-01-23 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 13:40 [PATCH net] ipv6: fix reachability confirmation with proxy_ndp Gergely Risko
2023-01-23 11:20 ` 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=167447281736.14272.18315324318489774078.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gergely.risko@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.