From: patchwork-bot+netdevbpf@kernel.org
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, dsahern@kernel.org,
gregkh@linuxfoundation.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, stable@vger.kernel.org,
edwin.brossette@6wind.com
Subject: Re: [PATCH net v3 1/2] ip: fix dflt addr selection for connected nexthop
Date: Thu, 14 Jul 2022 13:10:14 +0000 [thread overview]
Message-ID: <165780421418.729.15886797244518922619.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220713114853.29406-1-nicolas.dichtel@6wind.com>
Hello:
This series was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 13 Jul 2022 13:48:52 +0200 you wrote:
> When a nexthop is added, without a gw address, the default scope was set
> to 'host'. Thus, when a source address is selected, 127.0.0.1 may be chosen
> but rejected when the route is used.
>
> When using a route without a nexthop id, the scope can be configured in the
> route, thus the problem doesn't exist.
>
> [...]
Here is the summary with links:
- [net,v3,1/2] ip: fix dflt addr selection for connected nexthop
https://git.kernel.org/netdev/net/c/747c14307214
- [net,v3,2/2] selftests/net: test nexthop without gw
https://git.kernel.org/netdev/net/c/cd72e61bad14
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:[~2022-07-14 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 11:48 [PATCH net v3 1/2] ip: fix dflt addr selection for connected nexthop Nicolas Dichtel
2022-07-13 11:48 ` [PATCH net v3 2/2] selftests/net: test nexthop without gw Nicolas Dichtel
2022-07-14 13:10 ` 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=165780421418.729.15886797244518922619.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=edwin.brossette@6wind.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=stable@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