Has something happened to the ash1 tunnel server or further upstream somewhere?
Yesterday about 4:30~pm EDT both my office and home connections fail to load facebook and various other sites with ipv6 support. Chrome reports "Error 7 (net::ERR_TIMED_OUT): The operation timed out." Google ipv6 sites still load. If I disable the ipv6 address on the inside interface on the router ipv4 takes over and all is fine.
With ipv6 enabled internally you can see the trace makes it past the he.net network yet the trace does not complete.
bdavenport@CAG:~$ traceroute6 2a03:2880:10:8f01:face:b00c:0:25
traceroute to 2a03:2880:10:8f01:face:b00c:0:25 (2a03:2880:10:8f01:face:b00c:0:25) from 2001:470:8:303:213:2ff:fe5b:6fe2, 30 hops max, 16 byte packets
1 2001:470:8:303::1 (2001:470:8:303::1) 0.872 ms 0.643 ms 0.578 ms
2 mindlesstux-1.tunnel.tserv13.ash1.ipv6.he.net (2001:470:7:303::1) 43.391 ms 44.233 ms 44.851 ms
3 gige-g4-12.core1.ash1.he.net (2001:470:0:90::1) 43.744 ms 43.985 ms 48.98 ms
4 facebook-as32934.10gigabitethernet6.switch3.ash1.he.net (2001:470:0:1bf::2) 43.505 ms 42.891 ms 43.788 ms
5 ae2.bb01.iad1.tfbnw.net (2620:0:1cff:dead:beef::79) 41.694 ms 42.845 ms 41.963 ms
6 ae7.bb03.prn1.tfbnw.net (2620:0:1cff:dead:beef::11e) 130.356 ms 131.884 ms 137.51 ms
7 2620:0:1cff:dead:beef::13 (2620:0:1cff:dead:beef::13) 132.455 ms 133.015 ms 131.215 ms
8 2620:0:1cff:dead:beee::13f (2620:0:1cff:dead:beee::13f) 134.872 ms 135.752 ms 135.211 ms
9 * * *
10 * * *
11 * * *
12 * * *
Ping reaches though.
bdavenport@CAG:~$ ping6 -c 4 2a03:2880:10:8f01:face:b00c:0:25
PING 2a03:2880:10:8f01:face:b00c:0:25(2a03:2880:10:8f01:face:b00c:0:25) 56 data bytes
64 bytes from 2a03:2880:10:8f01:face:b00c:0:25: icmp_seq=1 ttl=50 time=134 ms
64 bytes from 2a03:2880:10:8f01:face:b00c:0:25: icmp_seq=2 ttl=50 time=135 ms
64 bytes from 2a03:2880:10:8f01:face:b00c:0:25: icmp_seq=3 ttl=50 time=134 ms
64 bytes from 2a03:2880:10:8f01:face:b00c:0:25: icmp_seq=4 ttl=50 time=134 ms
--- 2a03:2880:10:8f01:face:b00c:0:25 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 134.703/134.909/135.341/0.450 ms
Attached is a image from my routers gui on the trace to the same IP, as you can see it completes. But the issue from what I can tell is beyond the he.net network. Any ideas as to what the issue is and possible fix?
I'm seeing the same issue with the same symptoms through ash1.
Quote from: mindlesstux on June 23, 2012, 08:30:03 AM
bdavenport@CAG:~$ traceroute6 2a03:2880:10:8f01:face:b00c:0:25
8 2620:0:1cff:dead:beee::13f (2620:0:1cff:dead:beee::13f) 134.872 ms 135.752 ms 135.211 ms
9 * * *
etwork. Any ideas as to what the issue is and possible fix?
That IP is a FB IP, right?
It appears that is the final hop right after 2620:0:1cff:dead:beee::13f. So this to me appears to be a firewall issue or something along those lines at the far end (FB).
I can MTR to it just fine:
mtr -r -c 5 -n 2a03:2880:10:8f01:face:b00c:0:25
HOST: lnxjerry Loss% Snt Last Avg Best Wrst StDev
1.|-- 2001:470:xxxx:xxxx::1 0.0% 5 0.4 0.5 0.4 0.6 0.1
2.|-- 2001:470:xxxx:xxxx::1 0.0% 5 32.3 32.0 31.1 32.7 0.7
3.|-- 2001:470:0:6e::1 0.0% 5 28.6 29.4 27.9 30.6 1.1
4.|-- 2001:504:0:4:0:3:2934:1 0.0% 5 61.5 54.5 51.7 61.5 4.0
5.|-- 2620:0:1cff:dead:beef::23 0.0% 5 77.4 72.0 64.7 86.6 9.8
6.|-- 2620:0:1cff:dead:beee::10 0.0% 5 87.6 85.7 83.6 87.6 1.5
7.|-- 2620:0:1cff:dead:beef::e6 0.0% 5 99.2 102.1 99.2 105.0 2.1
8.|-- 2620:0:1cff:dead:beef::b 0.0% 5 104.1 104.6 103.4 106.1 1.3
9.|-- 2620:0:1cff:dead:beee::13 0.0% 5 109.0 104.2 102.3 109.0 2.8
10.|-- 2a03:2880:10:8f01:face:b0 20.0% 5 100.6 102.1 100.6 103.9 1.6
I'm also seeing this issue on Netflix.
Also seeing it on att "home page". In the office a few users reported their bank sites not working.
Since Unix-based platforms use UDP as default protocol for traceroute, so some destinations that did not allow UDP port range 33434-33534 will appear to be unreachable within the traceroute.
This is my result from Windows XP, which uses ICMP for traceroute:
C:\>tracert www.facebook.com
Tracing route to www.facebook.com [2a03:2880:10:8f01:face:b00c:0:25]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms gw-r01-pp.kh.v6.tnc92.net [2001:470:19:885:10::1
]
2 50 ms 50 ms 51 ms gawamakito-1.tunnel.tserv20.hkg1.ipv6.he.net [20
01:470:18:885::1]
3 47 ms 47 ms 47 ms gige-g3-13.core1.hkg1.he.net [2001:470:0:ba::1]
4 199 ms 196 ms 199 ms facebook-10G.hkix.net [2001:7fa:0:1::ca28:a16e]
5 196 ms 196 ms 198 ms ae23.bb01.sjc1.tfbnw.net [2620:0:1cff:dead:beef:
:479]
6 218 ms 220 ms 217 ms ae16.bb01.prn1.tfbnw.net [2620:0:1cff:dead:beef:
:fa]
7 218 ms 216 ms 217 ms ae0.dr05.prn1.tfbnw.net [2620:0:1cff:dead:beef::
33]
8 218 ms 221 ms 218 ms 2620:0:1cff:dead:beee::149
9 218 ms 216 ms 217 ms www6-10-08-prn1.facebook.com [2a03:2880:10:8f01:
face:b00c:0:25]
Trace complete.
You guys opened up trouble tickets right?
I'm seeing a similar issue as well, Facebook, YouTube, etc...
How do I go about opening a support ticket? (can't find the link for the life of me)
email ipv6@he.net
My issue cleared late yesterday by the time I checked the thread and saw broquea's question. It was bit late for me to make a reply the would have made any sense.