Peter Bieringer wrote: > sorry for requesting help here, but hopefully there are some > people on the > list who can check this world-wide (and perhaps the problem > and a solution) > > Me and some others to here in Germany have much troubles connecting to > www.deepspace6.net with 6to4 address as source: > > > Server has 2 IPv6 addresses: > 6bone: 3ffe:8300:0:1:10:a7ff:fe16:27f4
traceroute to deepspace6.net (3ffe:8300:0:1:10:a7ff:fe16:27f4) from 3ffe:8114:2000:240:290:27ff:fe24:c19f, 30 hops max, 16 byte packets 1 gw-20.ams-02.nl.sixxs.net (3ffe:8114:1000::26) 41.729 ms 18.702 ms 28.987 ms 2 Amsterdam.core.ipv6.intouch.net (2001:6e0::2) 44.545 ms 38.93 ms 19.663 ms 3 gw-viagenie-cnit.ipv6.cnit.it (3ffe:830f::3) 123.507 ms 134.928 ms 137.097 ms 4 gw-cnit-tilab.ipv6.cnit.it (3ffe:830f::c) 182.188 ms * 208.621 ms 5 gw-fe-na.ipv6.cnit.it (3ffe:8300::4) 220.987 ms * 207.466 ms 6 3ffe:8300:0:1:10:a7ff:fe16:27f4 (3ffe:8300:0:1:10:a7ff:fe16:27f4) 233.201 ms 235.604 ms 230.61 ms It's more that their prefix is oddly routed: traceroute to fs.ipv6.cnit.it (3ffe:8300:0:1:201:2ff:fe94:df20) from 3ffe:8114:2000:240:290:27ff:fe24:c19f, 30 hops max, 16 byte packets 1 gw-20.ams-02.nl.sixxs.net (3ffe:8114:1000::26) 32.863 ms 61.985 ms 20.157 ms 2 Amsterdam.core.ipv6.intouch.net (2001:6e0::2) 20.134 ms 20.513 ms 33.92 ms 3 gw-viagenie-cnit.ipv6.cnit.it (3ffe:830f::3) 123.253 ms 124.119 ms 131.484 ms 4 gw-cnit-tilab.ipv6.cnit.it (3ffe:830f::c) 183.053 ms * 205.704 ms 5 gw-fe-na.ipv6.cnit.it (3ffe:8300::4) 240.375 ms * 218.757 ms 6 * * fs.ipv6.cnit.it (3ffe:8300:0:1:201:2ff:fe94:df20) 375.714 ms Check hop 3 which effectively says it goes over viagenie... Let's inquiry the lookingglass (http://www.sixxs.net/tools/grh/lg/) and indeed most paths go over the US (viagenie and esnet) > Prod : 2001:760:204:10:10:a7ff:fe16:27f4 That doesn't even trace.. traceroute to 2001:760:204:10:10:a7ff:fe16:27f4 (2001:760:204:10:10:a7ff:fe16:27f4) from 3ffe:8114:2000:240:290:27ff:fe24:c19f, 30 hops max, 16 byte packets 1 gw-20.ams-02.nl.sixxs.net (3ffe:8114:1000::26) 19.376 ms 19.863 ms 18.647 ms 2 Amsterdam.core.ipv6.intouch.net (2001:6e0::2) 19.79 ms 18.625 ms 18.785 ms 3 gw.ipv6.lt (2001:778:11:5::1) 92.729 ms 97.113 ms 93.586 ms 4 se-gw.nordu.net (2001:6e0:0:10f::2) 149.247 ms 149.174 ms 149.116 ms 5 6net-gw.nordu.net (2001:948:0:f008::1) 149.569 ms 149.165 ms 149.517 ms 6 * * * 7 * * * 8 * No wonder IE doesn't want to open the site using IPv6... > > Problem exists since two weeks or so. > > Perhaps someone could check this from different 6to4 > addresses and/or look into routing tables of such routers. > > See traceroutes below for more. I rather think it is a problem at cnit then in the 6to4 setup. They really should be checking their routing tables. And clean them up a lot. Greets, Jeroen --------------------------------------------------------------------- The IPv6 Users Mailing List Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
