summaryrefslogtreecommitdiffstats
path: root/net/ipv6/Makefile
diff options
context:
space:
mode:
authorJakub Sitnicki <jkbs@redhat.com>2017-08-23 09:55:41 +0200
committerDavid S. Miller <davem@davemloft.net>2017-08-24 18:05:43 -0700
commit22b6722bfa591ba03d6a0c5521b600d4ab2d9a27 (patch)
tree9bf3a5238858962f1b7c006bc3c152862998bf4f /net/ipv6/Makefile
parent39a7e5892418514db114ea4842d7d88aee6a61b8 (diff)
downloadop-kernel-dev-22b6722bfa591ba03d6a0c5521b600d4ab2d9a27.zip
op-kernel-dev-22b6722bfa591ba03d6a0c5521b600d4ab2d9a27.tar.gz
ipv6: Add sysctl for per namespace flow label reflection
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@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv6/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud