|
Ticket ID: SIXXS #1059896 Ticket Status: Remote Problem PoP: fihel01 - DNA Oy (Helsinki)
Routing problems to reader.ipv6.xsnews.nl
![[fi]](/s/countries/fi.gif) Carmen Sandiego on Monday, 13 April 2009 15:27:26
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
There seems to be issue with connecting to reader.ipv6.xsnews.nl, I have already contacted to their support, they just told me that there is a problem with my tunnel. What i checked their forums, there are couple else SixXS users who are having hard times with connecting to this ipv6 usenet-server.
Using AICCU Console version(Vista x64) and connecting works to other hosts(ipv6.google.com for example).
Routing problems to reader.ipv6.xsnews.nl
![[de]](/s/countries/de.gif) Shadow Hawkins on Monday, 13 April 2009 17:20:25
If it is a routing problem it is rather widespread. I can't reach that server from any native location...
1 svr01.mucip.net (2001:4d88:1005::1) 0.489 ms
2 2001:4d88:ffff:ffff:d0:b76c:114f:1 (2001:4d88:ffff:ffff:d0:b76c:114f:1) 2.826 ms
3 2001:4d88::b (2001:4d88::b) 1.053 ms
4 nbg-s1-rou-1030.DE.eurorings.net (2001:7f8:29:1::65) 1.409 ms
5 asd2-rou-1030.eurorings.net (2001:680::134:222:86:48) 11.590 ms
6 2001:680:0:800f::3e (2001:680:0:800f::3e) 16.755 ms
7 2001:4de0:1000:a13::1 (2001:4de0:1000:a13::1) 13.809 ms
8 1-1.r2.am.v6.hwng.net (2001:4de0:1000:1::2) 13.186 ms
9 *
10 *
1 heimdall.oms16.birkenwald.de (2001:a60:f001:1::1) 0.361 ms
2 gw-1.muc-02.de.sixxs.net (2001:a60:f000::1) 5.957 ms
3 2001:a60:0:30::1 (2001:a60:0:30::1) 15.282 ms
4 10gigabitethernet1-4.core1.ams1.he.net (2001:470:0:47::1) 21.907 ms
5 2001:470:1:1f::2 (2001:470:1:1f::2) 43.490 ms
6 2001:4de0:1000:a13::1 (2001:4de0:1000:a13::1) 22.586 ms
7 1-1.r2.am.v6.hwng.net (2001:4de0:1000:1::2) 29.816 ms
8 *
9 *
1 backbone2-gige-0-3-15.teleport-iabg.de (2001:1b10:100:3::12) 4.839 ms
2 mchn-s1-rou-1030.DE.eurorings.net (2001:680:0:800f::a) 0.744 ms
3 asd2-rou-1030.eurorings.net (2001:680::134:222:86:48) 15.404 ms
4 2001:680:0:800f::3e (2001:680:0:800f::3e) 18.895 ms
5 2001:4de0:1000:a13::1 (2001:4de0:1000:a13::1) 24.155 ms
6 1-1.r2.am.v6.hwng.net (2001:4de0:1000:1::2) 21.355 ms
7 *
8 *
1 vl-23.csr1-2wr.lrz-muenchen.de (2001:4ca0:0:f000::1) 0.474 ms
2 xr-gar1-te1-3-108.x-win.dfn.de (2001:638:c:a003::1) 0.42 ms
3 zr-fra1-te0-7-0-1.x-win.dfn.de (2001:638:c:c043::2) 9.091 ms
4 de-cix.he.net (2001:7f8::1b1b:0:1) 7.886 ms
5 10gigabitethernet1-4.core1.ams1.he.net (2001:470:0:47::1) 14.868 ms
6 2001:470:1:1f::2 (2001:470:1:1f::2) 25.346 ms
7 2001:4de0:1000:a13::1 (2001:4de0:1000:a13::1) 54.873 ms
8 1-1.r2.am.v6.hwng.net (2001:4de0:1000:1::2) 58.355 ms
9 *
10 *
Routing problems to reader.ipv6.xsnews.nl
Carmen Sandiego on Monday, 13 April 2009 18:34:30
1 24 ms 24 ms 25 ms teredo-relay.proserve.nl [2001:828:101:1::101]
2 25 ms 54 ms 25 ms cr2.eun.nl.proserve.nl [2001:828:101:1::1]
3 25 ms 24 ms 33 ms pc-2.cr1.eun.proserve.nl [2001:828:101:15::2]
4 26 ms 25 ms 25 ms 10ge-amsix.eun.ipv6.as5580.net [2001:7f8:1::a500:5580:1]
5 24 ms 24 ms 25 ms reader.ipv6.xsnews.nl [2a02:10:103:9::10]
(that`s paste from XSNews support guy)
I just know, that someones(not SixXS-users) can reach that server fine.
Hopefully it`s easy to fix, if there`s something to fix.
State change: remoteproblem
The state of this ticket has been changed to remoteproblem
Routing problems to reader.ipv6.xsnews.nl
Which address are you tracerouting to? I get the following, which does not seem to touch the Highwinds infrastructure at all.
traceroute to reader.ipv6.xsnews.nl (2a02:10:103:9::10) from 2001:41e0:ff00:0:216:3eff:fe00:4, 30 hops max, 16 byte packets
1 xen-gw.zrh.sixxs.net (2001:41e0:ff00::1) 0.14 ms 0.242 ms 0.148 ms
2 ipman.zrh.sixxs.net (2001:41e0:fe00:1::1) 1.079 ms 1.449 ms 1.352 ms
3 ge0-3.br01.zrh254.ipv6.ip-man.net (2001:41e0:100::1) 0.693 ms 0.679 ms 0.586 ms
4 pos3-0.cr01.gva02.ipv6.ip-man.net (2001:41e0:1::11d) 4.478 ms 4.482 ms 4.484 ms
5 srp1-0.cr01.gva16.ipv6.ip-man.net (2001:41e0:1::3) 4.714 ms 4.655 ms 4.857 ms
6 pos2-0.br01.ams254.ipv6.ip-man.net (2001:41e0:1::1116) 22.325 ms 22.34 ms 22.402 ms
7 10ge-amsix.eun.ipv6.as5580.net (2001:7f8:1::a500:5580:1) 22.832 ms 30.505 ms 25.216 ms
8 reader.ipv6.xsnews.nl (2a02:10:103:9::10) 22.931 ms 22.771 ms 23.363 ms
But some routes do and those die off:
traceroute to reader.ipv6.xsnews.nl (2a02:10:103:9::10) from 2001:838:1:1:210:dcff:fe20:7c7c, 30 hops max, 16 byte packets
1 ge-1-3-0.breda.ipv6.concepts-ict.net (2001:838:1:1::1) 0.389 ms 0.374 ms 0.362 ms
2 2001:838:0:10::1 (2001:838:0:10::1) 2.27 ms 2.361 ms 2.267 ms
3 2001:838:5:4::2 (2001:838:5:4::2) 2.165 ms 2.182 ms 2.303 ms
4 ams-ix.he.net (2001:7f8:1::a500:6939:1) 2.908 ms 2.731 ms 2.604 ms
5 2001:470:1:1f::2 (2001:470:1:1f::2) 5.558 ms 5.817 ms 5.818 ms
6 2001:4de0:1000:a13::1 (2001:4de0:1000:a13::1) 3.141 ms 3.165 ms 3.074 ms
7 1-1.r2.am.v6.hwng.net (2001:4de0:1000:1::2) 9.055 ms 3.458 ms 3.102 ms
8 * *^C
From Highwinds though:
traceroute to reader.ipv6.xsnews.nl (2a02:10:103:9::10), 30 hops max, 80 byte packets
1 (2001:1af8:1:f006:218:74ff:fe46:3200) 0.405 ms 0.429 ms 0.466 ms
2 be25.crs.evo.leaseweb.net (2001:1af8::19) 1.314 ms 1.296 ms 1.264 ms
3 10ge-amsix.eun.ipv6.as5580.net (2001:7f8:1::a500:5580:1) 1.128 ms 1.173 ms 1.195 ms
4 reader.ipv6.xsnews.nl (2a02:10:103:9::10) 1.325 ms 1.153 ms 1.234 ms
I guess some transit/peerings are quite misconfigured. But these are remote issues though.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 14 April 2009 00:14:01
Posting is only allowed when you are