SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #408945
Ticket Status: Resolved

PoP: sesto01 - Availo (Stockholm)

IPv6 routing down
[se] Shadow Hawkins on Tuesday, 15 August 2006 13:18:57
Routing outside of Port80's IPv6 backbone isn't working orion:~# traceroute6 www.sixxs.net traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:16d8:ff00:109::2, 30 hops max, 16 byte packets 1 * * * 2 * * * 3 * * * It seems like they are having problems there, because routing inside Port80 is working. Tried to restart aiccu, but this didn't help at all :( EDIT: Another trace from SiXXS (HEANET) to SiXXS (Port80): ph0x@destiny:~$ sudo traceroute6 cl-266.sto-01.se.sixxs.net traceroute to cl-266.sto-01.se.sixxs.net (2001:16d8:ff00:109::2) from 2001:770:100:5b::2, 30 hops max, 16 byte packets 1 gw-92.dub-01.ie.sixxs.net (2001:770:100:5b::1) 64.222 ms 64.213 ms 64.205 ms 2 portia-vlan8.bh.core.hea.net (2001:770:18:8::1) 64.442 ms 64.317 ms 64.269 ms 3 ar1-cwt-po1.hea.net (2001:770:8:31::1) 64.776 ms 64.809 ms 64.662 ms 4 hyperion-gige4-1.cwt.core.hea.net (2001:770:400:e::1) 65.097 ms 65.654 ms 64.954 ms 5 luna-gige3-2.kil.core.hea.net (2001:770:400:11::2) 65.252 ms 65.141 ms 65.053 ms 6 gx-link.core.hea.net (2001:770:90:7::2) 65.006 ms 65.027 ms 64.982 ms 7 eth10-0-0.xr1.ams1.gblx.net (2001:7f8:1::a500:3549:1) 91.191 ms 85.233 ms 85.076 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * *
State change: confirmed Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 15 August 2006 16:18:22
Message is Locked
The state of this ticket has been changed to confirmed
IPv6 routing down
[ch] Jeroen Massar SixXS Staff on Tuesday, 15 August 2006 16:18:51
It seems more that their internal network is the problem. We have contacted them for details.
IPv6 routing down
[ch] Jeroen Massar SixXS Staff on Thursday, 17 August 2006 08:36:36
This problems has been resolved yesterday around 13:00 and is stable since.
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Thursday, 17 August 2006 08:36:43
Message is Locked
The state of this ticket has been changed to resolved
IPv6 routing down
[se] Carmen Sandiego on Friday, 18 August 2006 14:53:56
seems like it's still broken... myrd:/var/log# traceroute6 www.sixxs.net traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:16d8:ff21::6, 30 hops max, 16 byte packets 1 gw-26.sto-01.se.sixxs.net (2001:16d8:ff00:19::1) 13.363 ms 13.301 ms 13.103 ms 2 ge1-sto.cr1.hy-sto.se.p80.net (2001:16d8:2::81) 13.536 ms !N 14.127 ms !N 13.73 ms !N myrd:/var/log#
IPv6 routing down
[ch] Jeroen Massar SixXS Staff on Friday, 18 August 2006 15:07:54
Port80's IPv6 routing table seems to miss a couple of European destinations. They are investigating the cause.
State change: reopened Locked
[ch] Jeroen Massar SixXS Staff on Friday, 18 August 2006 15:07:59
Message is Locked
The state of this ticket has been changed to reopened
IPv6 routing down
[se] Carmen Sandiego on Friday, 18 August 2006 15:32:00
hehe yea it seems like some routes fell of the table =)
IPv6 routing down
[se] Shadow Hawkins on Friday, 18 August 2006 19:42:20
Well, something is broken anyway. Check out non-sixxs destinations: # ping6 -c 1 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 --- noc.sixxs.net ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms # ping6 -c 1 www.kame.net PING www.kame.net(orange.kame.net) 56 data bytes 64 bytes from orange.kame.net: icmp_seq=1 ttl=47 time=301 ms --- www.kame.net ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 301.690/301.690/301.690/0.000 ms # traceroute6 www.kame.net traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:16d8:ff00:60::2, 30 hops max, 16 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 fa-3-3.r04.asbnva01.us.bb.gin.ntt.net (2001:418:0:6000::5) 133.946 ms 140.666 ms 135.109 ms 9 xe-0-2-0.r20.asbnva01.us.bb.gin.ntt.net (2001:418:0:2000::9) 133.509 ms 133.322 ms 133.226 ms 10 p64-2-2-0.r20.mlpsca01.us.bb.gin.ntt.net (2001:418:0:2000::125) 201.434 ms 200.537 ms 200.209 ms 11 p64-1-3-0.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::1aa) 300.022 ms 301.18 ms 312.349 ms 12 xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net (2001:218:0:6000::1a) 300.218 ms 301.999 ms 301.74 ms 13 ge-3-0-0-5.a13.tokyjp01.jp.ra.gin.ntt.net (2001:218:2000:3005::14) 300.697 ms 300.542 ms 300.465 ms 14 2001:218:2000:5000::92 (2001:218:2000:5000::92) 301.293 ms 301.227 ms 301.647 ms 15 ve-4.nec2.yagami.wide.ad.jp (2001:200:0:1c04:230:13ff:feae:5b) 304.981 ms 303.637 ms 304.248 ms 16 lo0.alaxala1.k2.wide.ad.jp (2001:200:0:4800::7800:1) 303.669 ms 306.971 ms 303.441 ms 17 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 301.235 ms 301.062 ms 301.655 ms
IPv6 routing down
[ch] Jeroen Massar SixXS Staff on Friday, 18 August 2006 19:54:47
Note that SixXS doesn't take care of any of the routing, the ISP operating the PoP does. The routing tables at Port80 and OCCAID are currently missing some routes to certain destinations. They have been contacted and are looking into the problem. BTW, you might want to look at your setup, especially MTU, as the "* * *", aka non-replies don't happen from the PoP itself, see Traceroute for that.
IPv6 routing down
[se] Carmen Sandiego on Tuesday, 22 August 2006 23:37:08
Works for me now.
IPv6 routing down
[se] Shadow Hawkins on Wednesday, 23 August 2006 12:32:10
It works fine now. It appears my traceroute problem goes away when downgrading from the 20060806 aiccu version to the 2005-01-31 version. I'm on Debian sarge/i386, stock Debian 2.6.8 kernel. Actually, 20060806 also works, but only if 2005-01-31 has been activated (and shutdown) before running 20060806. Apparently nothing bad with the POP, only my setup. I'm sorry for the noise.
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Monday, 11 September 2006 13:07:25
Message is Locked
The state of this ticket has been changed to resolved
IPv6 routing down
[nl] Shadow Hawkins on Tuesday, 31 October 2006 18:50:23
Looks like it's down again. traceroute to anima.vanbaak.info (2001:888:152c:0:202:3fff:fedb:ddfc) from 2001:16d8:ffac:2::9, 30 hops max, 16 byte packets 1 gw-278.sto-01.se.sixxs.net (2001:16d8:ff00:115::1) 10.251 ms 9.79 ms 9.884 ms 2 ge1-sto.cr1.hy-sto.se.p80.net (2001:16d8:2::81) 10.221 ms !N 10.366 ms !N 10.366 ms !N anima.vanbaak.info is able to reach sixxs and orange.kame.net using ipv6 so I'm sure that host is working fine. michiel@anima:~> ping6 www.sixxs.net Tuesday 18:45:06 PING www.sixxs.net(noc.sixxs.net) 56 data bytes 64 bytes from noc.sixxs.net: icmp_seq=1 ttl=58 time=35.7 ms --- www.sixxs.net ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 35.719/35.719/35.719/0.000 ms
IPv6 routing down
[se] Shadow Hawkins on Tuesday, 31 October 2006 20:40:35
i cant even ping noc
user@hispan.se>ping6 -c 1 noc.sixxs.net PING6(56=40+8+8 bytes) 2001:16d8:ff32:1:20e:cff:fe5d:eed0 --> 2001:838:1:1:210:dcff:fe20:7c7c --- noc.sixxs.net ping6 statistics --- 1 packets transmitted, 0 packets received, 100.0% packet loss
State change: reopened Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 01 November 2006 04:40:55
Message is Locked
The state of this ticket has been changed to reopened
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Friday, 03 November 2006 02:20:28
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