Wrong last hop IPv6 Traceroute

26 views
Skip to first unread message

Vladislav Kravchenko

unread,
Jun 16, 2022, 9:47:31 PM6/16/22
to Ping & Net
The tool aways duplicates the last hop with IPv6 ICMP traceroute. For example:

Trace to kinopoisk.ru 
1 - 2a06:a004:f078:10:aaa1:59ff:fe19:103f 
2 - 2a06:a004:f078::1 
3 - 2a06:f900:1:100::1 
4 - 2001:7f8:20:101::208:93 
5 - 
6 - 2a02:6b8:0:1a00::fffe 
7 - 2a02:6b8::473 
8 - 2a02:6b8::473 
9 - 2a02:6b8::473 
10 - 2a02:6b8::473 
11 - 2a02:6b8::473 
12 - 2a02:6b8::473 
13 - 2a02:6b8::473 
14 - 2a02:6b8::473 
15 - 2a02:6b8::473 
16 - 2a02:6b8::473 
17 - 2a02:6b8::473 
18 - 2a02:6b8::473 
19 - 2a02:6b8::473 
20 - 2a02:6b8::473 
21 - 2a02:6b8::473 
22 - 2a02:6b8::473 
23 - 2a02:6b8::473 
24 - 2a02:6b8::473 
25 - 2a02:6b8::473 
26 - 2a02:6b8::473 
27 - 2a02:6b8::473 
28 - 2a02:6b8::473 
29 - 2a02:6b8::473

Android 12

Ulf

unread,
Jun 17, 2022, 2:51:18 AM6/17/22
to Ping & Net
That's odd. It works fine if I trace the IP address, but I can reproduce the issue when tracing the host name. Not sure why that would behave differently - need to look into it. Thanks for the heads-up!

Trace to 2a02:6b8::473

1 - 
2 - 2a02:8109:8001:47::1
3 - 2a02:8100:6:2::103:10c1
4 - 
5 - 
6 - 
7 - 2001:1900:5:3::435
8 - 
9 - 2001:1900:5:2:2::6e66
10 - 
11 - 2a02:6b8:0:1a00::fffe

12 - 2a02:6b8::473

Ulf

unread,
Jun 17, 2022, 11:41:13 AM6/17/22
to Ping & Net
This will be fixed in the next release. Until then, pinging the IPv6 address instead of the host name works fine.

Ulf

unread,
Aug 8, 2022, 9:46:51 AM8/8/22
to Ping & Net
With today's release, this has been fixed.
Reply all
Reply to author
Forward
0 new messages