dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
899
share rss forum feed

mind21_98

join:2006-05-13
San Diego, CA

[TWC] Anyone having problems with tunnelbroker.net tunnels?

Occasionally websites that are on both IPv6 and IPv4 will stop responding for 30 seconds or so (long enough to get the timeout page in Chrome), but if I push Reload they start working again. Routing problem at TWC, or something on HE's end? AFAIK IPv4 only sites don't have problems.

Oh, I'm using an AirPort Extreme to handle the IPv6 tunnel (with my SBG6580 in bridge mode), if that matters.



Suit Up

join:2003-07-21
Los Angeles, CA

I was having some slowness the other day (but it would still connect). And it's been fine today. I assume you're using the LA tunnel as well?

To really be able to tell where the problem lies, when you're having these problems, you should try running a traceroute to see where the connection is timing out.


mind21_98

join:2006-05-13
San Diego, CA

said by Suit Up:

I was having some slowness the other day (but it would still connect). And it's been fine today. I assume you're using the LA tunnel as well?

To really be able to tell where the problem lies, when you're having these problems, you should try running a traceroute to see where the connection is timing out.

Yep, using the LA tunnel. I'll definitely need to traceroute next time it happens, but the challenge is how short the issue lasts.

mind21_98

join:2006-05-13
San Diego, CA
reply to mind21_98

Now that I've watched things for a few days, it looks like IPv6 sites are simply failing at the "waiting for blah.com" stage in Chrome. I tried traceroute6 and noticed no anomalies, but here is a trace anyway during one of the failures:

traceroute6: Warning: facebook.com has multiple addresses; using 2a03:2880:10:8f01:face:b00c::25
traceroute6 to facebook.com (2a03:2880:10:8f01:face:b00c::25) from 2001:470:d:30e:dc66:c3c5:423a:603c, 64 hops max, 12 byte packets
 1  2001:470:d:30e::1  2.039 ms  2.360 ms  2.174 ms
 2  tmiw-1.tunnel.tserv15.lax1.ipv6.he.net  27.124 ms  27.836 ms  26.953 ms
 3  gige-g4-6.core1.lax1.he.net  22.338 ms  24.610 ms  24.483 ms
 4  10gigabitethernet1-3.core1.lax2.he.net  26.928 ms  31.104 ms  25.136 ms
 5  2001:504:13::5f  30.890 ms  29.989 ms  30.222 ms
 6  ae1.bb01.lax1.tfbnw.net  34.337 ms
    ae1.bb02.lax1.tfbnw.net  79.660 ms  33.181 ms
 7  xe-4-3-1.bb02.pao1.tfbnw.net  33.125 ms
    xe-4-0-1.bb01.pao1.tfbnw.net  32.572 ms
    xe-1-1-0.bb02.sjc1.tfbnw.net  30.641 ms
 8  ae12.bb02.prn1.tfbnw.net  51.865 ms  52.694 ms  52.453 ms
 9  ae1.dr05.prn1.tfbnw.net  51.968 ms
    ae0.dr06.prn1.tfbnw.net  57.568 ms
    ae1.dr05.prn1.tfbnw.net  54.200 ms
10  po1025.csw08b.prn1.tfbnw.net  53.050 ms  51.771 ms
    2620:0:1cff:dead:beee::149  53.199 ms
11  * * *
12  *^C
 

and a trace to the IPv4 endpoint for the tunnel:

traceroute to 66.220.18.42 (66.220.18.42), 64 hops max, 52 byte packets
 1  10.0.1.1  2.712 ms  0.606 ms  0.608 ms
 2  * * *
 3  76.167.4.221  11.318 ms  8.962 ms  8.660 ms
 4  72.129.2.32  20.932 ms  15.823 ms  16.448 ms
 5  72.129.1.0  22.849 ms  16.568 ms  15.209 ms
 6  66.109.6.102  33.168 ms  15.926 ms  15.684 ms
 7  66.109.6.135  16.115 ms
    107.14.19.138  14.065 ms
    66.109.6.135  13.836 ms
 8  66.109.9.206  16.443 ms
    208.50.254.25  13.909 ms
    64.208.205.153  16.313 ms
 9  64.209.105.42  23.611 ms  26.997 ms  22.396 ms
10  66.220.18.42  25.070 ms  21.517 ms  20.129 ms
 

At this point, I'm not sure what else would be causing this. :(


Suit Up

join:2003-07-21
Los Angeles, CA
reply to mind21_98

Hmm... I wonder if it might be DNS? Do you notice the problem more often with a site you haven't visited for a while or is it just sporadic? If it's the first, what DNS servers are you using?


mind21_98

join:2006-05-13
San Diego, CA

said by Suit Up:

Hmm... I wonder if it might be DNS? Do you notice the problem more often with a site you haven't visited for a while or is it just sporadic? If it's the first, what DNS servers are you using?

Currently using the default TWC DNS servers (209.18.47.61 and 209.18.47.62) through my AirPort Extreme. I do have both the IPv4 and IPv6 addresses of my router listed for DNS on my laptop though, not sure if that matters. I think it's sporadic but I'll keep an eye on it.

mind21_98

join:2006-05-13
San Diego, CA

1 recommendation

reply to mind21_98

Update: I switched to SixXS and I'm having a lot fewer problems. My latency over IPv6 is ~100ms+ though, making me think that my packets are bouncing across the country before going anywhere else.

Native IPv6 can't come soon enough.