SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #440241
Ticket Status: Resolved

PoP: sesto01 - Availo (Stockholm)

IPv6 routing down
[se] Carmen Sandiego on Tuesday, 31 October 2006 20:34:21
nafallo@ogre:~ $ ping6 2001:16d8:ff00:f5::1 PING 2001:16d8:ff00:f5::1(2001:16d8:ff00:f5::1) 56 data bytes 64 bytes from 2001:16d8:ff00:f5::1: icmp_seq=1 ttl=64 time=45.9 ms 64 bytes from 2001:16d8:ff00:f5::1: icmp_seq=2 ttl=64 time=30.4 ms nafallo@ogre:~ $ ping6 noc.sixxs.net PING noc.sixxs.net(noc.sixxs.net) 56 data bytes From ge1-sto.cr1.hy-sto.se.p80.net icmp_seq=1 Destination unreachable: No route From ge1-sto.cr1.hy-sto.se.p80.net icmp_seq=2 Destination unreachable: No route nafallo@ogre:~ $ ping6 ipv6.chat.freenode.net PING ipv6.chat.freenode.net(sterling.freenode.net) 56 data bytes From ge1-sto.cr1.hy-sto.se.p80.net icmp_seq=1 Destination unreachable: No route From ge1-sto.cr1.hy-sto.se.p80.net icmp_seq=2 Destination unreachable: No route
IPv6 routing down
[se] Shadow Hawkins on Tuesday, 31 October 2006 21:01:12
I get the same thing on my IPv6 tunnel.
IPv6 routing down
[us] Shadow Hawkins on Tuesday, 31 October 2006 21:49:34
I'm getting much the same thing. error@underground ~ $ ping6 goethe.freenode.net PING goethe.freenode.net(sterling.freenode.net) 56 data bytes From 505.ge0-0.cr1.ord1.us.occaid.net icmp_seq=0 Destination unreachable: No route error@underground ~ $ traceroute6 goethe.freenode.net traceroute to goethe.freenode.net (2001:898:2000:3::1), 30 hops max, 40 byte packets 1 gw-111.chi-01.us.sixxs.net (2001:4830:1500:6e::1) 101.581 ms 102.389 ms 101.373 ms 2 505.ge0-0.cr1.ord1.us.occaid.net (2001:4830:e5:5::1) 100.309 ms 101.382 ms 101.325 ms 3 505.ge0-0.cr1.ord1.us.occaid.net (2001:4830:e5:5::1)(N!) 100.944 ms (N!) 101.439 ms (N!) 101.385 ms
IPv6 routing down
[ch] Jeroen Massar SixXS Staff on Wednesday, 01 November 2006 04:46:14
uschi01 seems to be fine (at least now that I test it): jeroen@noc:~$ traceroute6 2001:4830:1500:6e::2 traceroute to 2001:4830:1500:6e::2 (2001:4830:1500:6e::2) from 2001:838:1:1:210:dcff:fe20:7c7c, 30 hops max, 16 byte packets 1 fe0.breda.ipv6.concepts-ict.net (2001:838:1:1::1) 0.421 ms 0.368 ms 0.342 ms 2 se2.ams-ix.ipv6.concepts-ict.net (2001:838:0:10::1) 1.992 ms 2.112 ms 1.986 ms 3 ge6-2-0.br0.ams3.nl.gbxs.net (2001:7f8:1::a500:9009:1) 2.36 ms 2.268 ms 2.459 ms 4 2001:1598:b031:2::2 (2001:1598:b031:2::2) 2.986 ms 3.292 ms 3.266 ms 5 ge2-0-0-44.br0.uklon1.realroute.net (2001:1598:a:3::2) 12.061 ms 10.865 ms 12.058 ms 6 2001:7f8:4::31f9:1 (2001:7f8:4::31f9:1) 11.152 ms 11.678 ms 11.084 ms 7 v3323-mpd.cr1.ewr1.us.occaid.net (2001:4830:fe:1010::2) 88.657 ms 88.23 ms 88.562 ms 8 67.ge0-0.cr1.ord1.us.occaid.net (2001:4830:ff:1301::2) 109.653 ms 109.111 ms 109.353 ms 9 sixxs-chcgil-gw.customer.occaid.net (2001:4830:e5:5::2) 109.241 ms 109.436 ms 109.431 ms 10 cl-111.chi-01.us.sixxs.net (2001:4830:1500:6e::2) 212.546 ms !H 209.825 ms !H 210.381 ms !H Except for the 'no host' part being odd, is this issue still there?
IPv6 routing down
[us] Shadow Hawkins on Tuesday, 31 October 2006 21:50:47
I get have the same problem with routing to sterling.freenode.net on usewr01. larry@xiaodiannao:~$ ping6 goethe.freenode.net PING goethe.freenode.net(sterling.freenode.net) 56 data bytes From 0.ge0-3.cr1.ewr1.us.occaid.net icmp_seq=1 Destination unreachable: No route Someone on freenode IRC #ipv6 reported the same problem on uschi01. ping6 to sterling.freenode.net works fine on a Hexago/freenet6 tunnel. Should additional tickets be filed for the usewr01 and uschi01 POPs that are experiencing the same problem?
IPv6 routing down
[us] Shadow Hawkins on Tuesday, 31 October 2006 22:00:13
Works fine on my Hurricane Electric tunnel, too: error@www2 ~ $ traceroute6 goethe.freenode.net traceroute to goethe.freenode.net (2001:898:2000:3::1), 30 hops max, 40 byte packets 1 2001:470:1f01:ffff::12b6 (2001:470:1f01:ffff::12b6) 23.526 ms 23.180 ms 23.211 ms 2 2001:470:1fff:2::26 (2001:470:1fff:2::26) 22.724 ms 22.984 ms 22.957 ms 3 3ffe:81d0:ffff:1::1 (3ffe:81d0:ffff:1::1) 25.505 ms 24.329 ms 24.716 ms 4 plt6-gate0.iij-america.net (2001:504:d::2) 24.650 ms 24.201 ms 24.619 ms 5 2001:48b0:bb00:f007::4006 (2001:48b0:bb00:f007::4006) 26.378 ms 25.957 ms 26.082 ms 6 2001:504:0:1::6453:1 (2001:504:0:1::6453:1) 109.582 ms 110.077 ms 111.031 ms 7 2001:5a0:500:100::2 (2001:5a0:500:100::2) 112.891 ms 112.222 ms 111.755 ms 8 2001:5a0:500:100::2 (2001:5a0:500:100::2) 113.089 ms 111.910 ms 111.806 ms 9 if-1-0.mcore3.laa-losangeles.ipv6.teleglobe.net (2001:5a0:100:200::2) 112.168 ms 111.621 ms 111.739 ms 10 if-4-0.mcore3.njy-newark.ipv6.teleglobe.net (2001:5a0:100:100::2) 112.453 ms 111.602 ms 111.888 ms 11 if-2-0.mcore4.njy-newark.ipv6.teleglobe.net (2001:5a0:f00::6) 114.740 ms 112.192 ms 112.299 ms 12 if-3-0.mcore3.lhx-london.ipv6.teleglobe.net (2001:5a0:f00:100::6) 185.495 ms 185.312 ms 186.622 ms 13 if-6-0.core1.ad1-amsterdam.ipv6.teleglobe.net (2001:5a0:1300::2) 199.276 ms 199.187 ms 198.778 ms 14 2001:5a0:200::5 (2001:5a0:200::5) 198.776 ms 198.861 ms 198.959 ms 15 ix-11-0-1-458.6bb1.ad1-amsterdam.ipv6.teleglobe.net (2001:5a0:200::32) 199.228 ms 199.087 ms 199.097 ms 16 so-0-0-2.r1-hfd1.nl.ionip.net (2001:898:1000:c8::2) 199.608 ms 199.763 ms 199.767 ms 17 sterling.freenode.net (2001:898:2000:3::1) 199.852 ms 199.886 ms 199.745 ms
IPv6 routing down
[ch] Jeroen Massar SixXS Staff on Wednesday, 01 November 2006 04:50:10
That something works somewhere else is irrelevant. Nice round-the-world routing though: US -> Japan -> LA,US-> NY,US, London,UK, Amsterdam ;)
IPv6 routing down
[ch] Jeroen Massar SixXS Staff on Wednesday, 01 November 2006 04:48:12
From which address are you tracing? Traceroutes help. Ping6 does not. Pinging IRC servers in general is a bad idea as they tend to be ratelimmited. Next to the fact that we really can't care less about IRC servers. And yes, you should open a seperate ticket, this ticket is about sesto01. (Though I would not be surprised if sesto01 issues are sort of related to us* issues)
IPv6 routing down
[se] Carmen Sandiego on Wednesday, 01 November 2006 10:49:55
Jeroen, want any more info from me for sesto01?
State change: confirmed Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 01 November 2006 04:43:00
Message is Locked
The state of this ticket has been changed to confirmed
IPv6 routing down
[ch] Jeroen Massar SixXS Staff on Wednesday, 01 November 2006 04:51:41
For clarity: this ticket is about sesto01, which indeed seems to have routing issues at this moment. The other PoPs are not affected (as far as we could test). If you think they are, open another ticket with that specific PoP in the ticket.
IPv6 routing down
[us] Shadow Hawkins on Wednesday, 01 November 2006 08:02:28
Thanks for the assistance. There seems to be no problem here either anymore so whatever Michael & I were experiencing on the us POPs must have been temporary. Sorry about posting the information about the us* POPs on the wrong ticket. It won't happen again. You guys run a top notch operation and an awesome public service! Thank you!
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Friday, 03 November 2006 02:19:57
Message is Locked
The state of this ticket has been changed to resolved

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker