netdev - Re: [PATCH] net: allow traceroute with a specified interface in a vrf

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: <20181026.160325.546566169884211166.davem@davemloft.net>
Date:   Fri, 26 Oct 2018 16:03:25 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     mmanning@...tta.att-mail.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH] net: allow traceroute with a specified interface in a
 vrf

From: Mike Manning <mmanning@...tta.att-mail.com>
Date: Fri, 26 Oct 2018 12:24:35 +0100

> Traceroute executed in a vrf succeeds if no device is given or if the
> vrf is given as the device, but fails if the interface is given as the
> device. This is for default UDP probes, it succeeds for TCP SYN or ICMP
> ECHO probes. As the skb bound dev is the interface and the sk dev is
> the vrf, sk lookup fails for ICMP_DEST_UNREACH and ICMP_TIME_EXCEEDED
> messages. The solution is for the secondary dev to be passed so that
> the interface is available for the device match to succeed, in the same
> way as is already done for non-error cases.
> 
> Signed-off-by: Mike Manning <mmanning@...tta.att-mail.com>

Applied.