[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <07f075bd-46a7-4298-953f-d0540759d694@kernel.org>
Date: Tue, 18 Nov 2025 11:18:34 -0700
From: David Ahern <dsahern@...nel.org>
To: azey <me@...y.net>
Cc: nicolasdichtel <nicolas.dichtel@...nd.com>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>, netdev <netdev@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] net/ipv6: allow device-only routes via the multipath API
On 11/18/25 9:47 AM, azey wrote:
> On 2025-11-18 17:04:38 +0100, David Ahern <dsahern@...nel.org> wrote:
>> There is really no reason to take a risk of a regression. If someone
>> wants ecmp with device only nexthops, then use the new nexthop infra to
>> do it.
>
> My initial reason was that device-only ECMP via `ip route` works with IPv4
> but not IPv6, so I thought it'd make sense to unify functionality - but if
> this is final I won't argue any further.
>
There was a push many years ago to align v4 and v6 as much as possible.
Certain areas - like ipv6 multipath - proved to be too difficult and
ended up causing regressions.
Powered by blists - more mailing lists