SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #7961722
Ticket Status: Remote Problem

PoP: noosl01 - Availo (Oslo)

routing issues - traceroute stopping at
[no] Shadow Hawkins on Friday, 05 October 2012 18:01:18
Hi, I have two tunnels connected to noosl01 from two separate locations and ISPs, they are both unable to connect to any IPv6 host. The immediate POP seems up and responding, but a traceroute from either of the locations seem to stop at 2001:16d8:1:1357::70 The full traceroute is attached below. Are there currently known routing issues? gamma kristianf # traceroute6 google.com traceroute to google.com (2a00:1450:400f:800::1005) from 2001:16d8:ee00:71::2, 30 hops max, 24 byte packets 1 gw-114.osl-01.no.sixxs.net (2001:16d8:ee00:71::1) 8.444 ms 39.532 ms 35.067 ms 2 sixxs-oslo-demarc0.cust.ip6.p80.net (2001:16d8:aaaa:4::2) 22.487 ms 39.709 ms 27.5 ms 3 2002-sixxs.cr0-r23.ver-osl.no.ip6.p80.net (2001:16d8:aaaa:4::1) 9.406 ms 7.265 ms 18.483 ms 4 2001:16d8:3::1 (2001:16d8:3::1) 16.117 ms 13.8 ms 9.413 ms 5 te3-2-r65.cr0-r74.shg5-got.se.ip6.p80.net (2001:16d8:1:1335::74) 13.15 ms 31.01 ms 24.185 ms 6 te2-3-r74.cr0-r72.gbl-cph.dk.ip6.p80.net (2001:16d8:1:1313::72) 16.887 ms 18.946 ms 19.109 ms 7 2001:16d8:1:1357::70 (2001:16d8:1:1357::70) 211.88 ms 206.622 ms 211.748 ms
State change: remoteproblem Locked
[ch] Jeroen Massar SixXS Staff on Friday, 05 October 2012 20:31:48
Message is Locked
The state of this ticket has been changed to remoteproblem
routing issues - traceroute stopping at
[ch] Jeroen Massar SixXS Staff on Friday, 05 October 2012 20:33:13
Are there currently known routing issues?
Except for this one, no. Unfortunately it is hard to see where this goes wrong as there is no traceroute from the Google side. I'll try to reach them though and see what can be done about this.
routing issues - traceroute stopping at
[no] Shadow Hawkins on Friday, 05 October 2012 20:37:58
I have exact problem. I'm connected to the same PoP, noosl01. It seems like I have only route problem outside Norway.
[****@cloud ~]$ traceroute6 google.com traceroute to google.com (2a00:1450:400f:800::100e) from 2001:16d8:eecc::2, 30 hops max, 24 byte packets 1 gw.ipv6.*****.net (2001:16d8:eecc::1) 0.348 ms 0.261 ms 0.264 ms 2 gw-383.osl-01.no.sixxs.net (2001:16d8:ee00:17e::1) 9.291 ms 8.946 ms 9.01 ms 3 sixxs-oslo-demarc0.cust.ip6.p80.net (2001:16d8:aaaa:4::2) 9.221 ms 9.205 ms 9.133 ms 4 2002-sixxs.cr0-r23.ver-osl.no.ip6.p80.net (2001:16d8:aaaa:4::1) 9.5 ms 9.62 ms 9.794 ms 5 2001:16d8:3::1 (2001:16d8:3::1) 9.641 ms 9.824 ms 9.636 ms 6 te3-2-r65.cr0-r74.shg5-got.se.ip6.p80.net (2001:16d8:1:1335::74) 13.858 ms 13.847 ms 13.687 ms 7 te2-3-r74.cr0-r72.gbl-cph.dk.ip6.p80.net (2001:16d8:1:1313::72) 17.574 ms 17.303 ms 17.477 ms 8 2001:16d8:1:1357::70 (2001:16d8:1:1357::70) 28.569 ms 28.544 ms 28.666 ms
=== When i trace route vg.no (norwegian newspaper) it works fine.
[****@cloud ~]$ traceroute6 vg.no traceroute to vg.no (2001:67c:21e0::16) from 2001:16d8:eecc::2, 30 hops max, 24 byte packets 1 gw.ipv6.****.net (2001:16d8:eecc::1) 0.341 ms 0.265 ms 0.189 ms 2 gw-383.osl-01.no.sixxs.net (2001:16d8:ee00:17e::1) 9.022 ms 9.09 ms 9.183 ms 3 sixxs-oslo-demarc0.cust.ip6.p80.net (2001:16d8:aaaa:4::2) 9.192 ms 8.979 ms 9.18 ms 4 2002-sixxs.cr0-r23.ver-osl.no.ip6.p80.net (2001:16d8:aaaa:4::1) 9.743 ms 9.674 ms 9.637 ms 5 2001:16d8:3::1 (2001:16d8:3::1) 9.591 ms 9.616 ms 9.781 ms 6 xe-1-3-0.cr1-osl2.n.bitbit.net (2001:7f8:12:1::3:9029) 9.805 ms 9.803 ms 9.974 ms 7 vlan-9.cs1-osl2.n.bitbit.net (2a02:c0:1:1::7) 12.696 ms 10.552 ms 10.379 ms 8 * * www.vg.no (2001:67c:21e0::16) 10.069 ms
Problem with outgoing trafic suddenly
[dk] Shadow Hawkins on Friday, 05 October 2012 20:51:33
I have read and followed the "Reporting Problems" section on the Contact page. I am removing these five pre-filled lines to demonstrate that I really read it. I am providing the full details as requested on the mentioned Contact page. If I do not remove this, then please ignore this message as I didn't read it anyway. ------------------------------------------------------------------------------>8 It seems like I'm unable to send trafic anylonger - is there a problem somewhere. Here is a traceroute to ipv6.google.com : traceroute to ipv6.l.google.com (2a00:1450:400c:c05::68) from 2001:16d8:dd00:147::2, 30 hops max, 16 byte packets 1 gw-328.cph-01.dk.sixxs.net (2001:16d8:dd00:147::1) 19.697 ms 20.733 ms 21.258 ms 2 sixxs-cph-demarc0.cust.ip6.p80.net (2001:16d8:aaaa:5::2) 21.621 ms 20.254 ms 21.794 ms 3 3229-sixxs.cr0-r72.gbl-cph.dk.ip6.p80.net (2001:16d8:aaaa:5::1) 21.453 ms 20.306 ms 21.531 ms 4 2001:16d8:1:1357::70 (2001:16d8:1:1357::70) 40.439 ms 46.596 ms 36.711 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * It seems like the problem is not at my end (I can also ping the PoP end of the tunnel just fine). Anyone else having problems?
Problem with outgoing trafic suddenly
[dk] Shadow Hawkins on Saturday, 06 October 2012 10:31:20
I have read and followed the "Reporting Problems" section on the Contact page. I am removing these five pre-filled lines to demonstrate that I really read it. I am providing the full details as requested on the mentioned Contact page. If I do not remove this, then please ignore this message as I didn't read it anyway. ------------------------------------------------------------------------------>8 Seems to be working again: traceroute to ipv6.l.google.com (2a00:1450:4008:c01::93) from 2001:16d8:dd00:147::2, 30 hops max, 16 byte packets 1 gw-328.cph-01.dk.sixxs.net (2001:16d8:dd00:147::1) 25.532 ms 23.506 ms 31.975 ms 2 sixxs-cph-demarc0.cust.ip6.p80.net (2001:16d8:aaaa:5::2) 25.367 ms 23.902 ms 23.615 ms 3 3229-sixxs.cr0-r72.gbl-cph.dk.ip6.p80.net (2001:16d8:aaaa:5::1) 25.993 ms 24.158 ms 23.685 ms 4 2001:16d8:1:1357::70 (2001:16d8:1:1357::70) 41.073 ms 40.632 ms 41.654 ms 5 amsix-router.google.com (2001:7f8:1::a501:5169:1) 48.851 ms 46.217 ms 45.599 ms 6 2001:4860::1:0:8 (2001:4860::1:0:8) 42.86 ms 41.366 ms 45.763 ms 7 2001:4860::8:0:2db0 (2001:4860::8:0:2db0) 42.055 ms 41.313 ms 42.572 ms 8 2001:4860::8:0:2e9c (2001:4860::8:0:2e9c) 56.934 ms 55.57 ms 55.747 ms 9 2001:4860::8:0:3097 (2001:4860::8:0:3097) 62.862 ms 77.304 ms 62.392 ms 10 2001:4860::2:0:6e0 (2001:4860::2:0:6e0) 58.84 ms 57.94 ms 57.986 ms 11 * * * 12 bk-in-x93.1e100.net (2a00:1450:4008:c01::93) 63.802 ms 61.782 ms 61.553 ms

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

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