netdev - Re: Query regarding IPV6 multipath (ECMP) routes in Linux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 15 Apr 2019 09:28:27 -0600
From:   David Ahern <dsahern@...il.com>
To:     Preethi Ramachandra <preethir@...iper.net>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Cc:     Silambu Chelvan M <silambu@...iper.net>,
        Yogesh Ankolekar <ayogesh@...iper.net>
Subject: Re: Query regarding IPV6 multipath (ECMP) routes in Linux

On 4/15/19 3:32 AM, Preethi Ramachandra wrote:
> 
> In IPV4 a single route is added with multipath nexthops. However, in IPV6 , multipath routes are added as separate single routes with each multipath NH. I wanted to understand why is this behaviour change in Linux for IPV6 multipath routes. Why wasn’t same IPV4 approach followed in this case?

IPv4 support for multipath existed first. IPv6 is fairly new.

If you move forward a few kernel versions there is a bit more
consistency between IPv4 and IPv6, but still there are annoying
differences and limitations due to IPv6 code guessing whether to make
gateway routes multipath or not (see rt6_qualify_for_ecmp).