SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #483779
Ticket Status: Resolved

PoP: simbx01 - Amis (Maribor)

Routing problems with simbx01
[ba] Shadow Hawkins on Saturday, 17 February 2007 14:14:29
Hi, I have a very strange routing problem. In the past few days I noticed that I could not reach one my IPv6 enabled servers in the UK. I am currently using the simbx01 POP. To confirm that it is not only my problem, I used your traceroute page and I have noticed that all of the IPv6 POPs that are passing thru 2001:608:0:e01::125 gateway cannot reach neither Slovenian POP or my IPv6 local IP address (same applies for my 6to4 enabled server in the UK). IPv6 POP: 2001:15c0:65ff:88::1 Local IPv6 address: 2001:15c0:65ff:88::2 Traceroute from iedub01, nlams05, fihel01, demuc02, demuc01 (and possibly some others) doesnt work (others do work, but they do not pass 2001:608:0:e01::125 gateway). Example traceroute: IPv6 traceroute IPv6 traceroute from demuc02.sixxs.net @ M"net Telekommunikations GmbH, AS8767 to 2001:15c0:65ff:88::2 : Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation 1. 2001:a60:0:200::1 0.0% 5 1.5 13.4 1.5 60.4 26.3 [.de] Germany 8767 rt4.muc1.m-online.net. 2. 2001:a60::89:0:1:1 0.0% 5 2.1 6.9 2.0 25.8 10.6 [.de] Germany 8767 rt-inxs.m-online.net. 3. 2001:7f8:2c:1000:0:a500:5539 0.0% 5 196.5 80.8 1.7 196.5 104.5 4. 2001:608:0:e01::125 0.0% 5 2.4 2.4 2.2 2.5 0.1 [.de] Germany 5539 SpaceNET AG Cisco-M-XX-G0-0-2102.Space.Net. 5. ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 Doing traceroute from my local IPv6 address (using aiccu) to the 2001:608:0:e01::125 gateway does not yield much success: traceroute to 2001:608:0:e01::125 (2001:608:0:e01::125) from 2001:15c0:65ff:88::2, 30 hops max, 16 byte packets 1 gw-137.mbx-01.si.sixxs.net (2001:15c0:65ff:88::1) 79.538 ms 74.938 ms 70.652 ms 2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 72.843 ms 74.317 ms 71.779 ms 3 M6-Tu6.Space.Net (2001:608:0:3::218f:1) 98.64 ms 101.878 ms 98.005 ms 4 Cisco-M-XII-Fa0-0.Space.Net (2001:608:0:10::115) 98.6 ms 102.25 ms 97.788 ms 5 * Tracerouting to nlams05.sixxs.net (as an example): traceroute to nlams05.sixxs.net (2001:610:1:80bb:192:87:102:107) from 2001:15c0:65ff:88::2, 30 hops max, 16 byte packets 1 gw-137.mbx-01.si.sixxs.net (2001:15c0:65ff:88::1) 79.224 ms 76.571 ms 73.534 ms 2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 73.146 ms 75.029 ms 72.842 ms 3 2001:890:600:8002::8447 (2001:890:600:8002::8447) 77.093 ms 74.012 ms 79.136 ms 4 bbcr02-fra4-decixii-a.six-de.net (2001:4b88:0:4:9:2::) 91.589 ms 93.545 ms 91.373 ms 5 bbcr01-ams-a26a.six-de.net (2001:4b88:0:4:2:1:11:10) 99.011 ms 109.878 ms 122.362 ms 6 XSR03.Asd002A.surf.net (2001:7f8:1::a500:1103:2) 101.767 ms 104.019 ms 101.472 ms 7 AZ-500.XSR01.Asd001A.surf.net (2001:610:e08:20::21) 109.31 ms 110.616 ms 108.224 ms 8 * Traceroute that works (nlams01): traceroute to nlams01.sixxs.net (2001:838:2:1:2a0:24ff:feab:3b53) from 2001:15c0:65ff:88::2, 30 hops max, 16 byte packets 1 gw-137.mbx-01.si.sixxs.net (2001:15c0:65ff:88::1) 80.5 ms 73.199 ms 71.904 ms 2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 73.177 ms 73.829 ms 73.216 ms 3 2001:890:600:8002::8447 (2001:890:600:8002::8447) 76.321 ms 79.62 ms 76.985 ms 4 bbcr02-fra4-decixii-a.six-de.net (2001:4b88:0:4:9:2::) 89.256 ms 93.736 ms 89.872 ms 5 bbcr01-ams-a26a.six-de.net (2001:4b88:0:4:2:1:11:10) 101.395 ms 105.538 ms 100.718 ms 6 ams-ix.ipv6.concepts.nl (2001:7f8:1::a501:2871:1) 104.159 ms 112.855 ms 107.432 ms 7 2001:838:0:10::2 (2001:838:0:10::2) 105.532 ms 112.372 ms 107.071 ms 8 2001:838:2:1:2a0:24ff:feab:3b53 (2001:838:2:1:2a0:24ff:feab:3b53) 104.814 ms 106.582 ms 104.289 ms Any chance of fixing this? Regards, Sergej
State change: confirmed Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 17 February 2007 15:12:38
Message is Locked
The state of this ticket has been changed to confirmed
Routing problems with simbx01
[ch] Jeroen Massar SixXS Staff on Saturday, 17 February 2007 15:37:59
Seems to indeed be some strange routing happening somewhere... $ traceroute6 simbx01.sixxs.net traceroute to simbx01.sixxs.net (2001:15c0:ffff:7::2) from 2001:a60:0:200::2, 30 hops max, 16 byte packets 1 rt4.muc1.m-online.net (2001:a60:0:200::1) 1.399 ms 1.441 ms 1.233 ms 2 rt-inxs.m-online.net (2001:a60::89:0:1:1) 65.32 ms 10.27 ms 2.059 ms 3 Cisco-M-XXI-G2-5.Space.net (2001:7f8:2c:1000:0:a500:5539:1) 107.118 ms 177.304 ms 2.102 ms 4 Cisco-M-XX-G0-0-2102.Space.Net (2001:608:0:e01::125) 1.96 ms 3.793 ms 2.322 ms 5 Cisco-M-XX-G0-0-2102.Space.Net (2001:608:0:e01::125) 2.099 ms !H * 2.115 ms !H
Routing problems with simbx01
[ba] Shadow Hawkins on Sunday, 18 February 2007 18:04:27
This seems to be fixed now, thanks! Sergej
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 20 February 2007 13:54:07
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