netdev - Re: [PATCH] Fix returned tc and hoplimit values for route with IPv6 encapsulation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20160327.223516.747400717075178298.davem@davemloft.net>
Date:	Sun, 27 Mar 2016 22:35:16 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	quentin@...itage.org.uk
Cc:	kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org,
	kaber@...sh.net, netdev@...r.kernel.org
Subject: Re: [PATCH] Fix returned tc and hoplimit values for route with
 IPv6 encapsulation

From: Quentin Armitage <quentin@...itage.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@...itage.org.uk>

Applied, thank you.