North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Bad IPv6 connectivity or why not to announce more specifics (Was:IPv6 news)

  • From: Nicholas Suan
  • Date: Thu Oct 13 17:28:30 2005 
[email protected] wrote:
Somehow, I don't think anything that Abilene does is going to fix Jordi's
routing. From where *you* are, do *you* have a path to 2001:0440:1880:1000::0020
that *doesn't go through Japan? If so, what does your path look like?

At least some parts of the US seem to.
This wouldn't be so bad if I didn't have to go across the US to get to the first hop:

[email protected]:~$ /usr/sbin/ntpdate -q 2001:0440:1880:1000::0020 192.36.143.234
server 2001:440:1880:1000::20, stratum 1, offset -0.005350, delay 0.27211
server 192.36.143.234, stratum 1, offset 0.002036, delay 0.15575
13 Oct 16:13:39 ntpdate[1526]: adjust time server 192.36.143.234 offset 0.002036 sec

[email protected]:~$ /usr/sbin/traceroute6 2001:0440:1880:1000::0020
traceroute to 2001:0440:1880:1000::0020 (2001:440:1880:1000::20) from 2001:470:1f00:ffff::649, 30 hops max, 16 byte packets
1 tommydool.tunnel.tserv1.fmt.ipv6.he.net (2001:470:1f00:ffff::648) 67.52 ms 70.567 ms 68.182 ms
2 2001:470:1fff:2::26 (2001:470:1fff:2::26) 67.607 ms 68.592 ms 70.168 ms
3 sl-bb1v6-rly-t-76.sprintv6.net (3ffe:2900:a:1::1) 143.214 ms 144.479 ms 145.113 ms
4 sl-s1v6-nyc-t-1000.sprintv6.net (2001:440:1239:1001::2) 150.654 ms 147.692 ms 151.378 ms
5 sl-bb1v6-sto-t-102.sprintv6.net (2001:440:1239:100d::2) 244.013 ms sl-bb1v6-sto-t-101.sprintv6.net (2001:440:1239:1012::1) 246.934 ms sl-bb1v6-sto-t-102.sprintv6.net (2001:440:1239:100d::2) 240.373 ms
6 2001:7f8:d:fb::34 (2001:7f8:d:fb::34) 262.842 ms 261.69 ms 263.779 ms
7 2001:440:1880:1::2 (2001:440:1880:1::2) 258.422 ms 266.312 ms 264.051 ms
8 2001:440:1880:1::12 (2001:440:1880:1::12) 250.289 ms 265.565 ms 267.93 ms
9 2001:440:1880:1000::20 (2001:440:1880:1000::20) 246.908 ms 249.03 ms 247.193 ms