From: Stephen Hemminger <stephen@networkplumber.org>
To: Robert Shearman <rshearma@brocade.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2 net-next 0/2] ip: Allow TTL propagation to/from IP packets to be configured
Date: Wed, 12 Apr 2017 10:00:28 -0700 [thread overview]
Message-ID: <20170412100028.22db144a@xeon-e3> (raw)
In-Reply-To: <1491834972-26668-1-git-send-email-rshearma@brocade.com>
On Mon, 10 Apr 2017 15:36:10 +0100
Robert Shearman <rshearma@brocade.com> wrote:
> This patch series adds support for per-MPLS-lightweight-tunnel ttl
> values and per route ttl-propagation for the purposes of MPLS to be
> specified.
>
> Robert Shearman (2):
> iproute: Add support for ttl-propagation attribute
> iproute: Add support for MPLS LWT ttl attribute
>
> ip/iproute.c | 22 ++++++++++++++++++++++
> ip/iproute_lwtunnel.c | 31 +++++++++++++++++++++++++++++--
> man/man8/ip-route.8.in | 19 +++++++++++++++++--
> 3 files changed, 68 insertions(+), 4 deletions(-)
>
Both applied, thanks
prev parent reply other threads:[~2017-04-12 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 14:36 [PATCH iproute2 net-next 0/2] ip: Allow TTL propagation to/from IP packets to be configured Robert Shearman
2017-04-10 14:36 ` [PATCH iproute2 net-next 1/2] iproute: Add support for ttl-propagation attribute Robert Shearman
2017-04-11 3:43 ` David Ahern
2017-04-11 8:35 ` Robert Shearman
2017-04-10 14:36 ` [PATCH iproute2 net-next 2/2] iproute: Add support for MPLS LWT ttl attribute Robert Shearman
2017-04-11 8:37 ` [PATCH v2 iproute2 net-next 0/2] ip: Allow TTL propagation to/from IP packets to be configured Robert Shearman
2017-04-11 8:37 ` [PATCH v2 iproute2 net-next 1/2] iproute: Add support for ttl-propagation attribute Robert Shearman
2017-04-11 22:37 ` David Ahern
2017-04-11 8:37 ` [PATCH v2 iproute2 net-next 2/2] iproute: Add support for MPLS LWT ttl attribute Robert Shearman
2017-04-11 22:37 ` David Ahern
2017-04-12 17:00 ` Stephen Hemminger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170412100028.22db144a@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=rshearma@brocade.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).