|
Subject |
Re: www.glif.is and IPv6 problems |
|
From |
Akira Kato <kato@xxxxxxxxxx> |
|
Date |
Thu, 19 Feb 2009 01:53:23 +0900 (JST) |
> traceroute to www.glif.is (2001:610:148:dead::6), 30 hops max, 80 byte packets
> 1 2001:468:c00:6::1 (2001:468:c00:6::1) 0.432 ms 0.542 ms 0.634 ms
> 2 2001:468:c00:5::2 (2001:468:c00:5::2) 1.581 ms 1.674 ms 1.765 ms
> 3 equinix.ash.cw.net (2001:504:0:2::1273:1) 3.077 ms 3.663 ms 3.077 ms
> 4 xe-11-0-0.xcr1.ash.cw.net (2001:5000:0:145::2) 95.519 ms 95.496 ms 95.507 ms
> 5 * * *
This traceroute shows that the 5th hop doesn't know how to reach you
rather than how to reach www.glif.is. I wonder if CW doesn't announce
your prefix. Please ask CW to identify what is the 5th hop.
What prefix MAX announces to CW? 2001:468::/32 (entire I2 prefix) or
portion of it covering MAX?
If MAX could prefer R&E paths over commercial ones, the situation
would change.
This type of problem happened frequently in the past in IPv4, and not
specific to IPv6 -- the problem remains while people are not serious
on IPv6 routing.
-- Akira Kato
