|
Ticket ID: SIXXS #14295185 Ticket Status: Remote Problem PoP: uslax03 - OCCAID Inc. (Los Angeles)
Routes to 2a00:: addresses seem to be broken
![[ca]](/s/countries/ca.gif) Shadow Hawkins on Monday, 21 September 2015 22:52:16
When attempting to reach 2a00:f70:abcd:102:0:1339:0:236, using TCP (ssh) or ping/traceroute, there seems to be a routing problem (perhaps a routing loop?) somewhere within the sixxs network. Or at least it looks that way, given that the traceroute output ends with sixxs hosts, but connectivity works from a site that doesn't use sixxs. Below is the output of traceroute, first from a system that connects through my sixxs tunnel, then from another site that doesn't use sixxs. The latter works.
~ (505) $ traceroute6 2a00:f70:abcd:102:0:1339:0:236
traceroute to 2a00:f70:abcd:102:0:1339:0:236 (2a00:f70:abcd:102:0:1339:0:236) from 2001:4830:1a00:12::2, 30 hops max, 24 byte packets
1 gw-19.lax-03.us.sixxs.net (2001:4830:1a00:12::1) 44.1 ms 44.407 ms 43.145 ms
2 uslax03.sixxs.net (2001:4830:ea::2) 43.155 ms 44.29 ms 41.931 ms
3 sixxs.lsan01.occaid.net (2001:4830:ea::1) 43.447 ms 43.359 ms 44.103 ms
4 sixxs.lsan01.occaid.net (2001:4830:ea::1) 44.015 ms !N 47.253 ms !N 43.782 ms !N
The traceroute command exits after the above. Ping and ssh fail too. When I try the same using the online traceroute service at http://centralops.net there is no problem. The traceroute output from that site is:
Tracing route to 2a00:f70:abcd:102:0:1339:0:236 [2a00:f70:abcd:102:0:1339:0:236]...
hop rtt rtt rtt ip address fully qualified domain name
1 0 0 0 2607:f0d0:1001:118::1 hexillion.com
2 0 0 0 2607:f0d0:1000:1::45 po101.dar01.sr01.dal01.networklayer.com
3 0 0 0 2607:f0d0:2:2::86 2607.f0d0.0002.0002.0000.0000.0000.0086-static.v6reverse.softlayer.com
4 20 20 20 2607:f0d0:2:2::7 po2.bbr02.tl01.atl01.networklayer.com
5 23 64 36 2001:478:132::75
6 44 33 42 2001:470:0:1b5::1 10ge14-13.core1.ash1.he.net
7 42 42 44 2001:470:0:299::2 100ge5-1.core1.nyc4.he.net
8 39 39 39 2001:2000:3080:1b8::1 nyk-111-s1-link.telia.net
9 118 118 118 2001:2000:3018:21::1 ddf-b2-v6.telia.net
10 118 118 118 2001:2000:3080:da9::2 comtrance-ic-312263-ddf-b2.c.telia.net
11 117 117 117 2a00:f70:aaaa:aaaa:0:1:0:6
12 122 122 122 2a00:f70:abcd:102:0:1339:0:165
13 117 117 117 2a00:f70:abcd:102:0:1339:0:236
Trace complete
Thanks,
Joachim
State change: remoteproblem
The state of this ticket has been changed to remoteproblem
Routes to 2a00:: addresses seem to be broken
there seems to be a routing problem (perhaps a routing loop?) somewhere within the sixxs network.
Please note that SixXS itself does not operate any network. The ISPs that operate the PoPs do.
4 sixxs.lsan01.occaid.net (2001:4830:ea::1) 44.015 ms !N 47.253 ms !N 43.782 ms !N
This clearly indicates that the OCCAID router (occaid.net) does not know where to route packets for that prefix (!N == network unreachable). Likely a transit issue.
Forwarding to OCCAID for resolution.
Routes to 2a00:: addresses seem to be broken
Shadow Hawkins on Saturday, 10 October 2015 08:00:53
You can close this ticket.
Although the SixXS tunnel was very reliable for many months, the delay in dealing with this ticket, together with draconian policies, which recently resulted in my tunnel getting disabled without prior notification while I was on vacation have convinced me that I do not want to rely on this service for my IPv6 connectivity. I've switched to a different tunnel provider.
Just to be clear, I'm grateful for your free service during the past months, and I'm not complaining, merely explaining the reasons why I'm going elsewhere.
Thank You
Joachim
Routes to 2a00:: addresses seem to be broken
Your email bounced, that is a problem that is on your side, we cannot do anything about your domain being properly available in DNS.
Every provider will have a requirement that the user is contactable. Disappearing from the Internet means you are not contactable.
|
![[ch]](/s/countries/ch.gif)
on Monday, 28 September 2015 07:08:24
Posting is only allowed when you are