SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #3099761
Ticket Status: Remote Problem

PoP: simbx01 - Amis (Maribor)

6to4 network not accesible via simbx01
[cz] Shadow Hawkins on Thursday, 25 November 2010 16:26:02
I am not able to reach 6to4 address 2002:c371:1236::1 via my sixx tunnel (simbx01). IPv6 traceroute from simbx01.sixxs.net @ Amis, AS8591 to 2002:c371:1236::1 : Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation 1. 2001:15c0:ffff:7::1 0.0% 5 0.7 0.7 0.6 1.2 0.2 2. 2001:15c0:ffff:d::3 0.0% 5 4.6 4.3 4.2 4.6 0.2 3. ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 I tried traceroute from other POP (plpoz01) and it works. IPv6 traceroute from plpoz01.sixxs.net @ Poznan Supercomputing and Networking Center, AS9112 to 2002:c371:1236::1 : Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation 1. 2001:808::7 0.0% 5 0.4 0.4 0.4 0.5 0.1 2. 2001:b10:c000:2::1 0.0% 5 0.7 0.5 0.4 0.7 0.1 3. 2001:948:2:a::1 0.0% 5 16.0 24.6 16.0 52.6 15.9 4. 2001:948:1:6::2 0.0% 5 16.2 16.2 16.2 16.3 0.0 5. 2001:948:1:4::3 0.0% 5 16.6 16.6 16.6 16.6 0.0 6. 2001:948:0:f052::2 0.0% 5 22.0 19.6 16.7 25.5 4.0 7. 2001:878:0:e000:82:e1:f4:1 0.0% 5 27.6 19.1 16.9 27.6 4.8 8. 2001:878:0:e000:82:e1:f4:91 0.0% 5 17.0 16.9 16.8 17.0 0.1 9. 2001:878:0:e000:82:e2:f9:fa 0.0% 5 16.9 16.9 16.8 17.0 0.1 10. 2002:c371:1236::1 0.0% 5 54.0 54.0 53.6 54.3 0.3 And it also works from native IPv6 connection.
State change: remoteproblem Locked
[ch] Jeroen Massar SixXS Staff on Thursday, 25 November 2010 16:37:50
Message is Locked
The state of this ticket has been changed to remoteproblem
6to4 network not accesible via simbx01
[ch] Jeroen Massar SixXS Staff on Thursday, 25 November 2010 16:38:33
Contact the remote site and ask them to figure this out, they chose to use 6to4, and debugging routing issues with 6to4 is near to impossible task.
6to4 network not accesible via simbx01
[cz] Shadow Hawkins on Saturday, 27 November 2010 09:56:47
I am the owner of the remote side and it does not look like routing issue with 6to4.
traceroute6 to gw-868.mbx-01.si.sixxs.net (2001:15c0:65ff:363::1) from 2002:c371:1236::1, 64 hops max, 12 byte packets 1 2002:c058:6301::1 1.331 ms 1.150 ms 1.264 ms 2 2001:1488::1 2.054 ms 1.086 ms 1.121 ms 3 2001:1488:d91f:cf88::8c 19.670 ms !P 20.924 ms !P 20.086 ms !P
traceroute to ext-router.virtlab.nomir.net (2002:c371:1236::1), 30 hops max, 80 byte packets 1 gw-868.mbx-01.si.sixxs.net (2001:15c0:65ff:363::1) 97.458 ms 100.935 ms 102.104 ms 2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 106.617 ms 110.270 ms 112.646 ms 3 vienna1-te-2-2.amis.net (2001:15c0:ffff:d::3) 119.383 ms 124.742 ms 128.265 ms 4 * * * 5 * * * 6 * * * 7 * * * 8 * * *
In one direction the communication ended on 2001:15c0:ffff:d::3 an in opposite direction on 2001:1488:d91f:cf88::8c - neither are 6to4. I have already contact owner of the 2001:1488:d91f:cf88::8c (nic-cz) - no reply yet. If anything can be done in your side please check it. I have used this connection very often. Thanks.

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

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