diff options
author | David S. Miller <davem@davemloft.net> | 2017-03-13 15:29:23 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-03-13 15:29:23 -0700 |
commit | 6a019c5c5059aa0d14788d015aba2f5934aa16ec (patch) | |
tree | f048a169201c566cd931aa29d17b0ce75c79e2aa /net/sunrpc/auth_generic.c | |
parent | b66239b6824f387361bf18747a7e93760ac3c0fb (diff) | |
parent | a59166e470868d92f0813977817e99e699398af5 (diff) | |
download | linux-6a019c5c5059aa0d14788d015aba2f5934aa16ec.tar.bz2 |
Merge branch 'mpls-ttl-propagation'
Robert Shearman says:
====================
mpls: allow TTL propagation from IP packets to be configured
Allow TTL propagation from IP packets to MPLS packets to be
configured. Add a new optional LWT attribute, MPLS_IPTUNNEL_TTL, which
allows the TTL to be set in the resulting MPLS packet, with the value
of 0 having the semantics of enabling propagation of the TTL from the
IP header (i.e. non-zero values disable propagation).
Also allow the configuration to be overridden globally by reusing the
same sysctl to control whether the TTL is propagated from IP packets
into the MPLS header. If the per-LWT attribute is set then it
overrides the global configuration. If the TTL isn't propagated then a
default TTL value is used which can be configured via a new sysctl,
"net.mpls.default_ttl". This is kept separate from the configuration
of whether IP TTL propagation is enabled as it can be used in the
future when non-IP payloads are supported (i.e. where there is no
payload TTL that can be propagated).
====================
Signed-off-by: Robert Shearman <rshearma@brocade.com>
Acked-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/sunrpc/auth_generic.c')
0 files changed, 0 insertions, 0 deletions