SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #888637
Ticket Status: Resolved

PoP: noosl01 - Availo (Oslo)

Connectivity between Your.org and Port80 broken with async HE/GBLX route
[dk] Carmen Sandiego on Monday, 29 December 2008 00:40:09
Hi Sixxs! I have trouble connecting to my server in the US (T17123/uschi02) from my AYIYA based tunnel (T16748/noosl01) over ipv6. I have also tried to use my other tunnel at home (T16780/noosl01) but it also fails with the below traceroute. As it seems there must be a routing problem between 2001:450:2008:1001::2 and 2001:470:0:36::1. If I need to provide more information please list what is relevant for this investigation. Traceroute from 2001:16d8:ee00:3b::2 to 2001:4978:f:1ab::2. 1 452 ms 28 ms 25 ms gw-60.osl-01.no.sixxs.net [2001:16d8:ee00:3b::1] 2 124 ms 26 ms * 3229-sixxs.cr0-r72.gbl-cph.dk.ip6.p80.net [2001:16d8:aaaa:4::1] 3 55 ms 203 ms 103 ms v1611-r23.cr0-r69.tc-sto.se.ip6.p80.net [2001:16 d8:1:1611::69] 4 37 ms 89 ms 202 ms v1315-r69.cr0-r84.kn1-sto.se.ip6.p80.net [2001:1 6d8:1:1315::84] 5 121 ms 179 ms 129 ms 2001:450:2002:17::1 6 151 ms 144 ms 162 ms 2001:450:2008:1001::2 7 183 ms 205 ms 216 ms 2001:450:2008:1001::2 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. Traceroute from 2001:4978:f:1ab::2 to 2001:16d8:ee00:3b::2. traceroute to 2001:16d8:ee00:3b::2 (2001:16d8:ee00:3b::2), 30 hops max, 40 byte packets 1 gw-428.chi-02.us.sixxs.net (2001:4978:f:1ab::1) 16.001 ms 24.002 ms 28.001 ms 2 sixxs.ge-0.0.0-30.core1.chi.bb6.your.org (2001:4978:1:400::ffff) 40.002 ms 44.002 ms 44.002 ms 3 gige-g2-19.core1.chi1.he.net (2001:470:0:7f::1) 32.001 ms 32.001 ms 32.001 ms 4 10gigabitethernet2-4.core1.nyc4.he.net (2001:470:0:4e::2) 52.003 ms 52.003 ms 56.003 ms 5 10gigabitethernet2-3.core1.ash1.he.net (2001:470:0:36::1) 60.003 ms 60.003 ms 60.003 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * [Admin Edit: Updated Subject]
FLDA-RIPE cant reach 2001:4978:f:1ab::2 to/from 2001:16d8:ee00:3b::2
[ch] Jeroen Massar SixXS Staff on Monday, 29 December 2008 11:04:38
There are unfortunately quite some issues (broken internal tunnelboxes and some other problems) inside the GBLX network (where 2001:450:2008:1001::2 is part of), which could already explain this issue, we've forwarded this problem report, lets hope it gets fixed over the weekend. The way back might be affected by this already. Apparently it is an issue inside HE.net whom are heaving heavy packet loss at their LINX node which also involves no packets passing through completely. Also notified Your.org so that the can monitor the issue too.
State change: confirmed Locked
[ch] Jeroen Massar SixXS Staff on Monday, 29 December 2008 00:20:16
Message is Locked
The state of this ticket has been changed to confirmed
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Monday, 29 December 2008 11:03:26
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