netdev - Re: Per-flow IPv4 ECMP

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <56094519.8030801@cumulusnetworks.com>
Date:	Mon, 28 Sep 2015 06:48:09 -0700
From:	roopa <roopa@...ulusnetworks.com>
To:	Matthew Dupre <Matthew.Dupre@...aswitch.com>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>, pch@...bogen.com
Subject: Re: Per-flow IPv4 ECMP

On 9/28/15, 1:57 AM, Matthew Dupre wrote:
> Hi,
>
> I'm interested in the Linux kernel's support for per-flow IPv4 ECMP (i.e. consistent path selection based on a hash of the connection tuple).  I'd been led to believe[1] that this depended on the route cache, which was removed in 3.6.
>
> However, I tested a route with multiple next hops on a 3.10 and 3.13 kernel, and ECMP was per-flow!  Obviously I'm pleased that this was the case, but I'd like to understand why this is supported, and whether I can rely on it in future.
>
> Could anyone give me a little clarification on whether this is now supported by some means other than the route cache, and whether that support is intended to be continued?
>
This is being worked on currently by Peter Nørlund
https://lwn.net/Articles/657431/
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html