[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <94d59fa1-cd13-5f43-ef1a-188e25f633ed@cumulusnetworks.com>
Date: Mon, 13 Mar 2017 12:43:06 -0600
From: David Ahern <dsa@...ulusnetworks.com>
To: Robert Shearman <rshearma@...cade.com>, davem@...emloft.net
Cc: netdev@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>,
roopa <roopa@...ulusnetworks.com>
Subject: Re: [PATCH net-next v3 2/2] mpls: allow TTL propagation from IP
packets to be configured
On 3/10/17 1:43 PM, Robert Shearman wrote:
> 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@...cade.com>
> ---
> Documentation/networking/mpls-sysctl.txt | 8 ++++
> include/net/mpls_iptunnel.h | 2 +
> include/net/netns/mpls.h | 1 +
> include/uapi/linux/mpls_iptunnel.h | 2 +
> net/mpls/af_mpls.c | 11 +++++
> net/mpls/mpls_iptunnel.c | 73 ++++++++++++++++++++++++++------
> 6 files changed, 84 insertions(+), 13 deletions(-)
Acked-by: David Ahern <dsa@...ulusnetworks.com>
Tested-by: David Ahern <dsa@...ulusnetworks.com>
Powered by blists - more mailing lists