From: David Miller <davem@davemloft.net>
To: quentin@armitage.org.uk
Cc: kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [PATCH] Fix returned tc and hoplimit values for route with IPv6 encapsulation
Date: Sun, 27 Mar 2016 22:35:16 -0400 (EDT) [thread overview]
Message-ID: <20160327.223516.747400717075178298.davem@davemloft.net> (raw)
In-Reply-To: <1459094771-24749-1-git-send-email-quentin@armitage.org.uk>
From: Quentin Armitage <quentin@armitage.org.uk>
Date: Sun, 27 Mar 2016 17:06:11 +0100
> For a route with IPv6 encapsulation, the traffic class and hop limit
> values are interchanged when returned to userspace by the kernel.
> For example, see below.
>
>># ip route add 192.168.0.1 dev eth0.2 encap ip6 dst 0x50 tc 0x50 hoplimit 100 table 1000
>># ip route show table 1000
> 192.168.0.1 encap ip6 id 0 src :: dst fe83::1 hoplimit 80 tc 100 dev eth0.2 scope link
>
> Signed-off-by: Quentin Armitage <quentin@armitage.org.uk>
Applied, thank you.
prev parent reply other threads:[~2016-03-28 2:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 16:06 [PATCH] Fix returned tc and hoplimit values for route with IPv6 encapsulation Quentin Armitage
2016-03-28 2:35 ` David Miller [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=20160327.223516.747400717075178298.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=quentin@armitage.org.uk \
--cc=yoshfuji@linux-ipv6.org \
/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).