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: <20150829.134628.1013990034021542524.davem@davemloft.net>
Date:	Sat, 29 Aug 2015 13:46:28 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	pch@...bogen.com
Cc:	netdev@...r.kernel.org, kuznet@....inr.ac.ru, jmorris@...ei.org,
	yoshfuji@...ux-ipv6.org, kaber@...sh.net,
	linux-api@...r.kernel.org, roopa@...ulusnetworks.com,
	sfeldma@...il.com, ebiederm@...ssion.com,
	nicolas.dichtel@...nd.com, tgraf@...g.ch, jbenc@...hat.com
Subject: Re: [PATCH v2 net-next 0/3] ipv4: Hash-based multipath routing

From: Peter Nørlund <pch@...bogen.com>
Date: Sat, 29 Aug 2015 22:31:15 +0200

> On Sat, 29 Aug 2015 13:14:29 -0700 (PDT)
> David Miller <davem@...emloft.net> wrote:
> 
>> From: pch@...bogen.com
>> Date: Fri, 28 Aug 2015 22:00:47 +0200
>> 
>> > When the routing cache was removed in 3.6, the IPv4 multipath
>> > algorithm changed from more or less being destination-based into
>> > being quasi-random per-packet scheduling. This increases the risk
>> > of out-of-order packets and makes it impossible to use multipath
>> > together with anycast services.
>> 
>> Don't even try to be fancy.
>> 
>> Simply kill the round-robin stuff off completely, and make hash based
>> routing the one and only mode, no special configuration stuff
>> necessary.
> 
> I like the sound of that! Just to be clear - are you telling me to
> stick with L3 and skip the L4 part?

For now it seems best to just do L3 and make ipv4 and ipv6 behave the
same.
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ