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
| ||
|
Date: Thu, 27 Oct 2016 11:23:31 -0400 (EDT) From: David Miller <davem@...emloft.net> To: jkbs@...hat.com Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH net-next 0/5] Route ICMPv6 errors with the flow when ECMP in use From: Jakub Sitnicki <jkbs@...hat.com> Date: Mon, 24 Oct 2016 11:28:47 +0200 > However, for it to work IPv6 flow labels have to be same in both > directions (i.e. reflected) or need to be chosen in a manner that > ensures that the flow going in the opposite direction would actually > be routed to a given path. My understanding is that this is not really guaranteed, and that entities are nearly encouraged to set the flow label in whatever manner makes sense for their use case. I think we really cannot have any kind of hard dependency on how flow labels are set and used by the internet.
Powered by blists - more mailing lists