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]

Date:	Tue, 29 Sep 2015 14:35:32 +0200
From:	Peter Nørlund <pch@...bogen.com>
To:	roopa <roopa@...ulusnetworks.com>
Cc:	Matthew Dupre <Matthew.Dupre@...aswitch.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Per-flow IPv4 ECMP

On Mon, 28 Sep 2015 06:48:09 -0700
roopa <roopa@...ulusnetworks.com> wrote:

> 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/

Hi,

AFAIK if you create a socket on the machine having the multipath route,
each socket will seemingly be mapped to particular path, and it will
behave as per-flow. But if you use the machine as a router, each packet
is forwarded independently, potentially hitting different paths each
time.

Best Regards
  Peter Nørlund
--
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