Pinging 2001:470:83f2::710:1 with 32 bytes of data:
Reply from 2001:470:83f2::710:1: TTL expired in transit.
Reply from 2001:470:83f2::710:1: TTL expired in transit.
Reply from 2001:470:83f2::710:1: TTL expired in transit.
The traceroute log shows there is loop between gige-gbge0.tserv3.fmt2.ipv6.he.net (2001:470:0:45::2) and 2001:470:1f05:46b:: (2001:470:1f05:46b::) ,
why does this happen ?
root@my-router:~# traceroute6 2001:470:83f2::710:1
traceroute to 2001:470:83f2::710:1 (2001:470:83f2::710:1) from 2001:470:xx:xxx::
2, 30 hops max, 16 byte packets
1 xxxxxxxx 462.937 ms 459.782 ms 464.646 ms
2 gige-g3-13.core1.hkg1.he.net (2001:470:0:ba::1) 471.736 ms 454.966 ms 445
.224 ms
3 gige-g3-7.core1.lax1.he.net (2001:470:0:16b::1) 601.472 ms 608.056 ms 623
.774 ms
4 10gigabitethernet7-3.core1.fmt2.he.net (2001:470:0:18d::1) 631.305 ms 621.
736 ms 629.472 ms
5 gige-gbge0.tserv3.fmt2.ipv6.he.net (2001:470:0:45::2) 629.212 ms 616.926 m
s 601.104 ms
6 2001:470:1f05:46b:: (2001:470:1f05:46b::) 610.83 ms 623.354 ms *
7 gige-gbge0.tserv3.fmt2.ipv6.he.net (2001:470:0:45::2) 644.836 ms 645.523 m
s 642.865 ms
8 2001:470:1f05:46b:: (2001:470:1f05:46b::) 643.052 ms 639.863 ms 652.648 m
s
9 * gige-gbge0.tserv3.fmt2.ipv6.he.net (2001:470:0:45::2) 767.077 ms 762.82
ms
10 2001:470:1f05:46b:: (2001:470:1f05:46b::) 756.582 ms 791.653 ms 775.611 m
s
11 gige-gbge0.tserv3.fmt2.ipv6.he.net (2001:470:0:45::2) 777.414 ms 773.525 m
s 783.549 ms
12 2001:470:1f05:46b:: (2001:470:1f05:46b::) 778.206 ms 767.727 ms 778.52 ms
789.084 mse0.tserv3.fmt2.ipv6.he.net (2001:470:0:45::2) 786.86 ms 782.569 ms
14 2001:470:1f05:46b:: (2001:470:1f05:46b::) 795.179 ms * 795.656 ms
15 gige-gbge0.tserv3.fmt2.ipv6.he.net (2001:470:0:45::2) 800.597 ms 795.223 m
s 796.268 ms
16 * 2001:470:1f05:46b:: (2001:470:1f05:46b::) 815.287 ms 805.07 ms
17 gige-gbge0.tserv3.fmt2.ipv6.he.net (2001:470:0:45::2) 814.652 ms * 816.663
ms
18 2001:470:1f05:46b:: (2001:470:1f05:46b::) 799.654 ms 801.1 ms 813.977 ms
19 gige-gbge0.tserv3.fmt2.ipv6.he.net (2001:470:0:45::2) 830.469 ms 824.854 m
s 800.938 ms
20 * 2001:470:1f05:46b:: (2001:470:1f05:46b::) 838.427 ms *
21 gige-gbge0.tserv3.fmt2.ipv6.he.net (2001:470:0:45::2) 843.727 ms 820.448 m
s 822.849 ms
22 2001:470:1f05:46b:: (2001:470:1f05:46b::) 837.593 ms *
It does look like there's a routing loop
Who/what is 2001:470:83f2::710:1?
Looks like an HE address, so I'd email ipv6@he.net and let them know.
And, no need to block out IP addresses, makes troubleshooting much harder
Man thats some crazy latency to the first hop as well.
1 xxxxxxxx 462.937 ms 459.782 ms 464.646 ms
That high of an address off a tserv would be a routed /48. If it's being kicked back to the tserv, that means the person who it's routed to doesn't have a route for it themselves and is left with going to default (back to the tserv).
Quote from: johnpoz on June 22, 2011, 09:42:34 AM
Man thats some crazy latency to the first hop as well.
1 xxxxxxxx 462.937 ms 459.782 ms 464.646 ms
Yes，I'm in China, and connect from home to the he.net Tunnel Server in US, so the latency can't be low...
Sigh~ :(
There are closer tunnel endpoints than the U.S. for you: Hong Kong and Singapore.
Quote from: snarked on July 06, 2011, 11:04:26 AM
There are closer tunnel endpoints than the U.S. for you: Hong Kong and Singapore.
Most US endpoints are better than HK or SG for China user. Chinese internet sux!
That may be true once network topography is determined, but there's no way any of us can tell that for him (except if we have a direct peering with his network).
Quote from: hunreal on July 09, 2011, 08:54:21 AM
Quote from: snarked on July 06, 2011, 11:04:26 AM
There are closer tunnel endpoints than the U.S. for you: Hong Kong and Singapore.
Most US endpoints are better than HK or SG for China user. Chinese internet sux!
Yes, you are right, I checked the ping result of those endpoints, the US endpoint is better, so i selected it.
I'm using a 10M fiber FTTH connection direct to my home, it's fast enough to open the websites in China, but the connection to US is poor.