netdev - Re: [PATCH net-next] ipv6: Add sysctl for per namespace flow label reflection

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

Message-Id: <20170824.180553.1621054459411024798.davem@davemloft.net>
Date:   Thu, 24 Aug 2017 18:05:53 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     jkbs@...hat.com
Cc:     netdev@...r.kernel.org, hannes@...essinduktion.org,
        nikolay@...ulusnetworks.com, tom@...bertland.com
Subject: Re: [PATCH net-next] ipv6: Add sysctl for per namespace flow label
 reflection

From: Jakub Sitnicki <jkbs@...hat.com>
Date: Wed, 23 Aug 2017 09:55:41 +0200

> Reflecting IPv6 Flow Label at server nodes is useful in environments
> that employ multipath routing to load balance the requests. As "IPv6
> Flow Label Reflection" standard draft [1] points out - ICMPv6 PTB error
> messages generated in response to a downstream packets from the server
> can be routed by a load balancer back to the original server without
> looking at transport headers, if the server applies the flow label
> reflection. This enables the Path MTU Discovery past the ECMP router in
> load-balance or anycast environments where each server node is reachable
> by only one path.
> 
> Introduce a sysctl to enable flow label reflection per net namespace for
> all newly created sockets. Same could be earlier achieved only per
> socket by setting the IPV6_FL_F_REFLECT flag for the IPV6_FLOWLABEL_MGR
> socket option.
> 
> [1] https://tools.ietf.org/html/draft-wang-6man-flow-label-reflection-01
> 
> Signed-off-by: Jakub Sitnicki <jkbs@...hat.com>

Ok, applied.