Fr0ken routes?

[Chris P. Ross]

Jason <jslagle@toledolink.com> said:
> bash-2.03$ traceroute6 www.kame.net
> traceroute to kame212.kame.net (3ffe:501:4819:2000:5054:ff:fedc:50d2), 30
> hops max, 12 byte packets
>  1  ipv6  3.148 ms *  2.748 ms
>  2  3ffe:1cff:0:f3::1  39.249 ms  30.795 ms  30.747 ms
>  3  3ffe:1cff:0:ee::2  73.608 ms *  72.616 ms
>  4  * vbns-uunetusgw62-tun2.ash.vbns.net  214.749 ms *
>  5  vbns-fibertel.dng.vbns.net  775.229 ms  781.812 ms  798.044 ms
>  6  * * *
>  7  *

> Wondering is anyone know who's fault this is :D

  Hmm.  I'm not sure what's going on there.  I can get there alright
from one of my IPv6 routers (one of which is hop #3 in your
traceroute), but not the other (which is the one connected to hop #4
in your traceroute).

  I'm not totally sure why hop 3 hits hop 4, but it's probabaly just
an addressing issue.  (vbns-uunetusgw61-tun1.ash.vbns.net is the
address connected to the box listed in hop #3)  a matter of which
address shows up from your point of view...

  I think it looks alright from my end, it just gets into VBNS and
doesn't seem to be acting normally.  I'll let them speak up.  If
there's anything I'm doing wrong, I presume they'll tell me.  :-)

                               - Chris

--
Chris P. Ross				UUNET Technologies, Inc.
cross@eng.us.uu.net			R & D / Engineering
cross@uu.net