On Mon, 28 Sep 2015 06:48:09 -0700 roopa <ro...@cumulusnetworks.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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
