Jeroen Massar wrote:
> 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)
this really seems to be a problem in the cnit routing config. gianluca,
perhaps you can check this problem?
> > 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...
are you sure? i can trace your host from ds6:
[EMAIL PROTECTED] mauro]$ /usr/sbin/traceroute6 -s 2001:760:204:10:10:a7ff:fe16:27f4
3ffe:8114:2000:240:290:27ff:fe24:c19f
traceroute to 3ffe:8114:2000:240:290:27ff:fe24:c19f
(3ffe:8114:2000:240:290:27ff:fe24:c19f) from
2001:760:204:10:10:a7ff:fe16:27f4, 30 hops max, 16 byte packets
1 2001:760:204:10:202:16ff:febc:1fc1 (2001:760:204:10:202:16ff:febc:1fc1) 1.366 ms
* 0.791 ms
2 3ffe:830f::a (3ffe:830f::a) 76.262 ms * 67.166 ms
3 3ffe:8100:102::1:6 (3ffe:8100:102::1:6) 175.268 ms 179.469 ms 187.643 ms
4 3ffe:8120::19:2 (3ffe:8120::19:2) 208.773 ms 232.596 ms 202.754 ms
5 ipng.nl (2001:6e0::250:4ff:fe4a:7708) 190.97 ms 181.706 ms 182.735 ms
6 3ffe:8114:2000:240:290:27ff:fe24:c19f (3ffe:8114:2000:240:290:27ff:fe24:c19f)
219.356 ms 228.461 ms 215.707 ms
[EMAIL PROTECTED] mauro]$ /usr/sbin/traceroute6 -s 3ffe:8300:0:1:10:a7ff:fe16:27f4
3ffe:8114:2000:240:290:27ff:fe24:c19f
traceroute to 3ffe:8114:2000:240:290:27ff:fe24:c19f
(3ffe:8114:2000:240:290:27ff:fe24:c19f) from
3ffe:8300:0:1:10:a7ff:fe16:27f4, 30 hops max, 16 byte packets
1 3ffe:8300:0:1:202:16ff:febc:1fc1 (3ffe:8300:0:1:202:16ff:febc:1fc1) 0.948 ms *
1.07 ms
2 3ffe:8300::5 (3ffe:8300::5) 24.308 ms * 25.03 ms
3 3ffe:8100:102::1:6 (3ffe:8100:102::1:6) 189.886 ms 212.803 ms 202.296 ms
4 3ffe:b00:c18::61 (3ffe:b00:c18::61) 290.605 ms 300.884 ms 290.953 ms
5 ipng.nl (2001:6e0::250:4ff:fe4a:7708) 297.034 ms 295.936 ms 292.553 ms
6 3ffe:8114:2000:240:290:27ff:fe24:c19f (3ffe:8114:2000:240:290:27ff:fe24:c19f)
310.646 ms 316.277 ms 342.222 ms
the production address should be reachable from any network which is
connected to the 6net. perhaps there is a routing problem between
your host/net and the 6net.
> > 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.
well, we must be able to track down the problem before we can fix it ;-)
are we really sure that this is a problem with the cnit BGP RT?
--
Aequam memento rebus in arduis servare mentem...
Mauro Tortonesi [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Deep Space 6 - IPv6 with Linux http://www.deepspace6.net
Ferrara Linux User Group http://www.ferrara.linux.it
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
