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

[Valdis.Kletnieks () vt edu]

On Fri, 14 Oct 2005 10:21:20 EDT, Jared Mauch said:

>       Mine does not:
>
> punk:~/Desktop> traceroute6 2001:0440:1880:1000::0020
> traceroute to 2001:0440:1880:1000::0020 (2001:440:1880:1000::20) from 2001:418:3f4:0:20e:a6ff:febf:a5ca, 30 hops max, 
> 16 byte packets
>  1  2001:418:3f4::1 (2001:418:3f4::1)  3.95 ms  1.342 ms  1.266 ms
>  2  2001:418:2400:5000::1 (2001:418:2400:5000::1)  15.109 ms  16.2 ms  15.136 ms
>  3  ae0-4.r01.chcgil06.us.bb.verio.net (2001:418:0:7056::1)  15.652 ms  15.417 ms  15.683 ms
>  4  p16-1-1-1.r21.snjsca04.us.bb.verio.net (2001:418:0:2000::2a9)  62.209 ms  61.899 ms  62.196 ms
>  5  p64-0-0-0.r20.mlpsca01.us.bb.verio.net (2001:418:0:2000::235)  63.7 ms  63.328 ms  64.479 ms
>  6  xe-1-1.r02.mlpsca01.us.bb.verio.net (2001:418:0:2000::35)  62.185 ms  63.449 ms  62.941 ms
>  7  fa-0-0-0.r00.mlpsca01.us.b6.verio.net (2001:418:0:700f::b600)  62.942 ms  63.405 ms  64.565 ms
>  8  tu-0.sprint.mlpsca01.us.b6.verio.net (2001:418:0:4000::4a)  64.486 ms  65.586 ms  65.215 ms
>  9  sl-s1v6-nyc-t-1001.sprintv6.net (2001:440:1239:1005::2)  137.216 ms sl-bb1v6-nyc-t-1001.sprintv6.net 
> (2001:440:1239:100b::1)  135.68 ms sl-s1v6-nyc-t-1001.sprintv6.net (2001:440:1239:1005::2)  137.073 ms

Interesting. :)  That's the first one I've seen that a sprintv6.net address isn't at
hop number 3 or so (indicating that the person is basically directly connected to
sprintv6.net) and also doesn't take a loop through Japan....

Attachment: _bin
Description: