Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: can't reach us.archive.ubuntu.com from sixxs, traceroute dies in HE network  (Read 2080 times)

buddyp

  • Newbie
  • *
  • Posts: 3

Hi,

I've had a sixxs tunnel up at Ashburn for about a year and its been great. I really appreciate them supporting an IPv6  educational effort but they have been less than helpful with this problem and I don't really know where to go for help. The problem traceroute ends in HE's network so I thought I'd try here.

Recently, I have been unable to reach us.archive.ubuntu.com via the sixxs tunnel. I am not sure if this used to work and broke, or Ubuntu recently added IPv6 and its been broken since they started. Regardless, it doesn't work now. All I know for sure is before last week 'apt-get update' worked and now it doesn't. I never paid any attention to whether it was IPv4 or IPv6 until it stopped working :(

Code: [Select]
joel@homestar:~$ traceroute6 us.archive.ubuntu.com
traceroute to us.archive.ubuntu.com (2001:67c:1562::14) from 2001:4830:xxxx:xxxx::xxxx, 30 hops max, 24 byte packets
 1  asus-ap6 (2001:4830:xxxx:xxxx::xxxx)  0.55 ms  0.387 ms  0.458 ms
 2  gw-xxxx.qas-01.us.sixxs.net (2001:4830:xxxx:xxxx::xxxx)  15.167 ms  10.844 ms  12.543 ms
 3  sixxs-asbnva-gw.customer.occaid.net (2001:4830:e6:7::2)  10.264 ms  9.461 ms  9.711 ms
 4  iad0-b0-ge2.hotnic.net (2001:4810:0:100::1)  12.378 ms  11.802 ms  12.364 ms
 5  10gigabitethernet2-2.core1.ash1.he.net (2001:504:0:2::6939:1)  12.852 ms  14.163 ms  22.095 ms
 6  100ge5-1.core1.nyc4.he.net (2001:470:0:299::2)  17.835 ms  19.178 ms  25.44 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  *^C

I have another location that has native IPv6 from comcast and I don't have any problems reaching it from there:

Code: [Select]
root@SurfsUp:~# traceroute6 us.archive.ubuntu.com
traceroute to us.archive.ubuntu.com (2001:67c:1562::16) from 2001:558:6020:178:xxxx:xxxx:xxxx:xxxx, 30 hops max, 16 byte packets
 1  2001:558:6020:xxxx::x (2001:558:6020:xxxx::x)  30.951 ms  28.077 ms  17.031 ms
 2  xe-11-3-0-32767-sur01.oceancity.md.bad.comcast.net (2001:558:342:8015::1)  8.561 ms  10.545 ms  8.827 ms
 3  2001:558:340:44e::1 (2001:558:340:44e::1)  12.803 ms  13.945 ms  12.786 ms
 4  he-5-2-0-0-11-cr01.ashburn.va.ibone.comcast.net (2001:558:0:f6bd::1)  16.837 ms  17.848 ms  16.6 ms
 5  be-14-pe03.350ecermak.il.ibone.comcast.net (2001:558:0:f8b4::2)  15.313 ms  14.723 ms  15.871 ms
 6  2001:559::d16 (2001:559::d16)  15.652 ms  15.458 ms  14.1 ms
 7  be2112.mpd22.dca01.atlas.cogentco.com (2001:550:0:1000::9a36:5ea)  16.434 ms  15.046 ms  15.4 ms
 8  be2151.ccr42.jfk02.atlas.cogentco.com (2001:550:0:1000::9a36:284a)  19.955 ms  20.428 ms  20.418 ms
 9  be2096.ccr22.bos01.atlas.cogentco.com (2001:550:0:1000::9a36:1e2a)  26.441 ms  25.832 ms  25.51 ms
10  2001:550:2:2c::15:2 (2001:550:2:2c::15:2)  26.455 ms  25.413 ms  25.409 ms
11  economy.canonical.com (2001:67c:1562::16)  26.037 ms  29.853 ms  26.174 ms

It looks to me like there is a problem with a route advertisement, but I don't know enough to figure out where it is. Perhaps someone here knows how to do that so I can take my problem to the right place?

Thanks!
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1722

There are like a bajillion threads on here (or maybe 5) about how Occaid/TowardEX has screwed up routing to their transits and aren't announcing their IPv6 ranges back to HE. Traces from HE die at XO/Internap or Telia/Internap. So its been looking like an Occaid/TowardEX issue with Internap.
Logged

buddyp

  • Newbie
  • *
  • Posts: 3

Thanks for the quick reply. The moral of the story is search first :) 

I went to the ubuntu bug tracker and clicked "affects me" on that issue. Hopefully ubuntu will notice since it affects security updates and that they will have more traction with TowardEX than us mere users do.

For now the solution that solves my problem is to:
Code: [Select]
cat > /etc/apt/apt.conf.d/99force-ipv4
Acquire::ForceIPv4 "true";
^d
« Last Edit: January 23, 2015, 12:54:01 PM by buddyp »
Logged