netdev - Re: [PATCH net-next] net: icmp6: provide input address for traceroute6

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]

Date:   Sun, 03 Nov 2019 17:27:45 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     fruggeri@...sta.com
Cc:     kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
        netdev@...r.kernel.org
Subject: Re: [PATCH net-next] net: icmp6: provide input address for
 traceroute6

From: fruggeri@...sta.com (Francesco Ruggeri)
Date: Wed, 30 Oct 2019 17:40:02 -0700

> traceroute6 output can be confusing, in that it shows the address
> that a router would use to reach the sender, rather than the address
> the packet used to reach the router.
> Consider this case:
> 
>         ------------------------ N2
>          |                    |
>        ------              ------  N3  ----
>        | R1 |              | R2 |------|H2|
>        ------              ------      ----
>          |                    |
>         ------------------------ N1
>                   |
>                  ----
>                  |H1|
>                  ----
> 
> where H1's default route is through R1, and R1's default route is
> through R2 over N2.
> traceroute6 from H1 to H2 shows R2's address on N1 rather than on N2.
> 
> The script below can be used to reproduce this scenario.
 ...
> Signed-off-by: Francesco Ruggeri <fruggeri@...sta.com>
> Original-patch-by: Honggang Xu <hxu@...sta.com>

Applied.