|
ipv6 Xsnews no longer reachable from nlams05 PoP
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Saturday, 04 December 2010 17:32:17
Since a few days my connection to the ipv6 newsgroups of xsnews is down. When I do a traceroute you can see that its no longer reachable. Anybody got simular issues or knows a way how to fix this.
traceroute6 reader.ipv6.xsnews.nl
ipv6 Xsnews no longer reachable from nlams05 PoP
![[dk]](/s/countries/dk.gif) Shadow Hawkins on Saturday, 04 December 2010 20:13:13
Ok here:
traceroute6: Warning: reader.ipv6.xsnews.nl has multiple addresses; using 2001:67c:174:101::3
traceroute6 to reader.ipv6.xsnews.nl (2001:67c:174:101::3) from 2001:16d8:dd00:c5::2, 64 hops max, 12 byte packets
1 gw-198.cph-01.dk.sixxs.net 24.992 ms 26.760 ms 27.121 ms
2 3229-sixxs.cr0-r72.gbl-cph.dk.ip6.p80.net 27.573 ms 27.327 ms 27.577 ms
3 te4-3-r72.cr0-r70.tc2-ams.nl.ip6.p80.net 168.504 ms 163.444 ms 135.505 ms
4 te4-1-r70.cr0-r71.the-lnd.uk.ip6.p80.net 47.004 ms 44.791 ms 46.304 ms
5 10ge-linx.r1.lon1.uk.as5580.net 61.094 ms 50.261 ms 54.630 ms
6 r2.ams5.nl.as5580.net 60.911 ms 53.961 ms 52.706 ms
7 as48345-gw.r2.ams5.nl.as5580.net 52.982 ms
as48345-gw.r2.ams5.nl.as5580.net 53.678 ms 57.382 ms
8 20ge-r1.as48345.net 58.581 ms 53.025 ms
2001:67c:174:101::3 54.215 ms
ipv6 Xsnews no longer reachable from nlams05 PoP
Shadow Hawkins on Saturday, 04 December 2010 20:14:52
Or by ip:
traceroute6 to 2001:67c:174:101::4 (2001:67c:174:101::4) from 2001:16d8:dd00:c5::2, 64 hops max, 12 byte packets
1 2001:16d8:dd00:c5::1 25.165 ms 25.049 ms 25.363 ms
2 2001:16d8:aaaa:5::1 27.832 ms 26.347 ms 26.859 ms
3 2001:16d8:1:1308::70 37.457 ms 37.204 ms 38.629 ms
4 2001:16d8:1:1327::71 45.560 ms 45.583 ms 45.313 ms
5 2001:7f8:4::15cc:1 47.541 ms 51.719 ms 49.026 ms
6 2a02:d28:5580::1:29 51.235 ms 66.246 ms 53.215 ms
7 2a02:d28:5580:1::3304:2 51.489 ms
2a02:d28:5580:1::3302:2 52.488 ms 54.175 ms
8 2001:67c:174:101::4 52.696 ms 52.444 ms
2001:67c:174::1:1 54.246 ms
ipv6 Xsnews no longer reachable from nlams05 PoP
Shadow Hawkins on Saturday, 04 December 2010 22:26:05
Hello Niek,
I experience the same problem as you mentioned. My first thought was that there was something wrong at XSnews, but a ping and trace from a ipv6 pingwebsite proves it was something with my SixXS tunnel.
Local at my PC with the SixXS tunnel, I got dead packets and traces don`t reach their destination. It seems some of the links aren't working at this moment.
ipv6 Xsnews no longer reachable from nlams05 PoP
Shadow Hawkins on Sunday, 05 December 2010 00:22:44
Ok I will give it a few more days to see if the problem gets solved. Seems like the issue is located within the Netherlands from the nlams05 PoP
ipv6 Xsnews no longer reachable from nlams05 PoP
Shadow Hawkins on Sunday, 05 December 2010 20:48:09
Same problem here, also nlams05 - SURFnet.
ipv6 Xsnews no longer reachable from nlams05 PoP
Shadow Hawkins on Monday, 06 December 2010 02:55:41
I have the same issue at the nlede01 PoP. Packets simply don't arrive.
traceroute6 reader.ipv6.xsnews.nl
traceroute to reader.ipv6.xsnews.nl (2001:67c:174:101::4), 30 hops max, 40 byte packets
1 gw-736.ede-01.nl.sixxs.net (2001:7b8:2ff:2df::1) 4.457 ms 4.522 ms 4.487 ms
2 sixxs-gw.jun1.bit-1.network.bit.nl (2001:7b8:3:4f::2) 4.672 ms 4.658 ms 4.626 ms
3 20ge-amsix.r2.ams5.nl.ipv6.as5580.net (2001:7f8:1::a500:5580:1) 8.833 ms 8.803 ms 8.772 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
ipv6 Xsnews no longer reachable from nlams05 PoP
Shadow Hawkins on Tuesday, 07 December 2010 19:29:58
Was about to open a ticket, but that isn't needed as it is working again now.
Hopefully it working for the both of you also now.
|
Posting is only allowed when you are