HE IPv6 tunnel problems
I've been experiencing IPv6 connectivity issues all this week, and had to disable my tunnel completely last night. Anyone experiencing any problems with HE IPv6 tunnels?
root@alpha:~# traceroute6 ipv6.google.com traceroute to ipv6.google.com (2607:f8b0:4005:802::1002), 30 hops max, 80 byte packets 1 redacted-2.tunnel.tserv1.den1.ipv6.he.net (2001:470:39:223:) 71.129 ms 76.464 ms 76.487 ms 2 ge2-19.core1.den1.he.net (2001:470:0:24b::1) 76.536 ms 80.735 ms 81.544 ms 3 10ge4-3.core1.chi1.he.net (2001:470:0:1af::1) 107.123 ms 107.152 ms 107.186 ms 4 google-as15169.10gigabitethernet7.switch2.chi1.he.net (2001:470:0:bf::2) 107.302 ms 114.789 ms 114.014 ms 5 2001:4860::1:0:92e (2001:4860::1:0:92e) 112.507 ms 112.537 ms 130.409 ms 6 2001:4860::8:0:5900 (2001:4860::8:0:5900) 120.730 ms 2001:4860::8:0:5901 (2001:4860::8:0:5901) 91.607 ms * 7 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 102.758 ms 2001:4860::8:0:64da (2001:4860::8:0:64da) 112.617 ms 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 106.705 ms 8 2001:4860::8:0:3427 (2001:4860::8:0:3427) 116.717 ms 2001:4860::8:0:3426 (2001:4860::8:0:3426) 118.457 ms 2001:4860::8:0:3427 (2001:4860::8:0:3427) 118.777 ms 9 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.603 ms 2001:4860::8:0:2cb6 (2001:4860::8:0:2cb6) 123.749 ms 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.057 ms 10 2001:4860::1:0:7ea (2001:4860::1:0:7ea) 135.940 ms 138.026 ms 137.344 ms 11 2001:4860:0:1::693 (2001:4860:0:1::693) 132.675 ms 134.535 ms 116.313 ms 12 2607:f8b0:4005:802::15 (2607:f8b0:4005:802::15) 118.554 ms 119.782 ms 115.659 ms Denver endpoint in case it wasn't clear from the traceroute. Could you elaborate on the issues you're seeing? Regards, SG On 5/7/2014 7:27 AM, Joshua M Boniface wrote:
I've been experiencing IPv6 connectivity issues all this week, and had to disable my tunnel completely last night. Anyone experiencing any problems with HE IPv6 tunnels? _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
The problem I've been seeing is specifically with service connectivity. I'm on the Toronto, ON tunnel. Pings and traceroutes complete without any problems, however as soon as services (specifically mail-related, IMAP and SMTP) were run across the tunnel, they would time out and fail. I'm just looking to see if anyone else has noticed something similar over the past few days. On 14-05-07 10:14 AM, Spencer Gaw wrote:
root@alpha:~# traceroute6 ipv6.google.com traceroute to ipv6.google.com (2607:f8b0:4005:802::1002), 30 hops max, 80 byte packets 1 redacted-2.tunnel.tserv1.den1.ipv6.he.net (2001:470:39:223:) 71.129 ms 76.464 ms 76.487 ms 2 ge2-19.core1.den1.he.net (2001:470:0:24b::1) 76.536 ms 80.735 ms 81.544 ms 3 10ge4-3.core1.chi1.he.net (2001:470:0:1af::1) 107.123 ms 107.152 ms 107.186 ms 4 google-as15169.10gigabitethernet7.switch2.chi1.he.net (2001:470:0:bf::2) 107.302 ms 114.789 ms 114.014 ms 5 2001:4860::1:0:92e (2001:4860::1:0:92e) 112.507 ms 112.537 ms 130.409 ms 6 2001:4860::8:0:5900 (2001:4860::8:0:5900) 120.730 ms 2001:4860::8:0:5901 (2001:4860::8:0:5901) 91.607 ms * 7 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 102.758 ms 2001:4860::8:0:64da (2001:4860::8:0:64da) 112.617 ms 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 106.705 ms 8 2001:4860::8:0:3427 (2001:4860::8:0:3427) 116.717 ms 2001:4860::8:0:3426 (2001:4860::8:0:3426) 118.457 ms 2001:4860::8:0:3427 (2001:4860::8:0:3427) 118.777 ms 9 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.603 ms 2001:4860::8:0:2cb6 (2001:4860::8:0:2cb6) 123.749 ms 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.057 ms 10 2001:4860::1:0:7ea (2001:4860::1:0:7ea) 135.940 ms 138.026 ms 137.344 ms 11 2001:4860:0:1::693 (2001:4860:0:1::693) 132.675 ms 134.535 ms 116.313 ms 12 2607:f8b0:4005:802::15 (2607:f8b0:4005:802::15) 118.554 ms 119.782 ms 115.659 ms
Denver endpoint in case it wasn't clear from the traceroute. Could you elaborate on the issues you're seeing?
Regards,
SG
On 5/7/2014 7:27 AM, Joshua M Boniface wrote:
I've been experiencing IPv6 connectivity issues all this week, and had to disable my tunnel completely last night. Anyone experiencing any problems with HE IPv6 tunnels? _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Hmmm, looks like you might be on to something. From HE6in4: root@alpha:~# for i in `dig mx gmail.com +short | cut -d' ' -f2` ; do printf "%-25s%-25s" "`date '+%x %X'`" "`dig AAAA $i +short`" ; e=`curl -6 -sSm 5 $i:25 2>&1 >/dev/null`; r=$?; echo "$e $r" ; done 05/07/2014 11:19:09 AM 2607:f8b0:4002:c01::1b curl: (28) connect() timed out! 28 05/07/2014 11:19:15 AM 2607:f8b0:400e:c03::1a curl: (28) connect() timed out! 28 05/07/2014 11:19:20 AM 2607:f8b0:4001:c03::1a curl: (28) connect() timed out! 28 05/07/2014 11:19:25 AM 2607:f8b0:400d:c04::1a curl: (28) connect() timed out! 28 05/07/2014 11:19:30 AM 2607:f8b0:400c:c01::1a curl: (28) connect() timed out! 28 From native IPv6: root@test:~# for i in `dig mx gmail.com +short | cut -d' ' -f2` ; do printf "%-25s%-25s" "`date '+%x %X'`" "`dig AAAA $i +short`" ; e=`curl -6 -sSm 5 $i:25 2>&1 >/dev/null`; r=$?; echo "$e $r" ; done 05/07/2014 11:14:29 AM 2607:f8b0:4001:c03::1a 0 05/07/2014 11:14:29 AM 2607:f8b0:400d:c04::1a 0 05/07/2014 11:14:29 AM 2607:f8b0:400c:c01::1a 0 05/07/2014 11:14:30 AM 2a00:1450:400c:c05::1b 0 05/07/2014 11:14:30 AM 2a00:1450:4013:c00::1a 0 No issues with IPv6 web traffic though. Anyone else seeing this? Regards, SG On 5/7/2014 8:32 AM, Joshua M Boniface wrote:
The problem I've been seeing is specifically with service connectivity. I'm on the Toronto, ON tunnel. Pings and traceroutes complete without any problems, however as soon as services (specifically mail-related, IMAP and SMTP) were run across the tunnel, they would time out and fail. I'm just looking to see if anyone else has noticed something similar over the past few days.
On 14-05-07 10:14 AM, Spencer Gaw wrote:
root@alpha:~# traceroute6 ipv6.google.com traceroute to ipv6.google.com (2607:f8b0:4005:802::1002), 30 hops max, 80 byte packets 1 redacted-2.tunnel.tserv1.den1.ipv6.he.net (2001:470:39:223:) 71.129 ms 76.464 ms 76.487 ms 2 ge2-19.core1.den1.he.net (2001:470:0:24b::1) 76.536 ms 80.735 ms 81.544 ms 3 10ge4-3.core1.chi1.he.net (2001:470:0:1af::1) 107.123 ms 107.152 ms 107.186 ms 4 google-as15169.10gigabitethernet7.switch2.chi1.he.net (2001:470:0:bf::2) 107.302 ms 114.789 ms 114.014 ms 5 2001:4860::1:0:92e (2001:4860::1:0:92e) 112.507 ms 112.537 ms 130.409 ms 6 2001:4860::8:0:5900 (2001:4860::8:0:5900) 120.730 ms 2001:4860::8:0:5901 (2001:4860::8:0:5901) 91.607 ms * 7 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 102.758 ms 2001:4860::8:0:64da (2001:4860::8:0:64da) 112.617 ms 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 106.705 ms 8 2001:4860::8:0:3427 (2001:4860::8:0:3427) 116.717 ms 2001:4860::8:0:3426 (2001:4860::8:0:3426) 118.457 ms 2001:4860::8:0:3427 (2001:4860::8:0:3427) 118.777 ms 9 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.603 ms 2001:4860::8:0:2cb6 (2001:4860::8:0:2cb6) 123.749 ms 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.057 ms 10 2001:4860::1:0:7ea (2001:4860::1:0:7ea) 135.940 ms 138.026 ms 137.344 ms 11 2001:4860:0:1::693 (2001:4860:0:1::693) 132.675 ms 134.535 ms 116.313 ms 12 2607:f8b0:4005:802::15 (2607:f8b0:4005:802::15) 118.554 ms 119.782 ms 115.659 ms
Denver endpoint in case it wasn't clear from the traceroute. Could you elaborate on the issues you're seeing?
Regards,
SG
On 5/7/2014 7:27 AM, Joshua M Boniface wrote:
I've been experiencing IPv6 connectivity issues all this week, and had to disable my tunnel completely last night. Anyone experiencing any problems with HE IPv6 tunnels? _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
FWIW, through Fremont with a BGP tunnel: bash-3.2$ for i in `dig mx gmail.com +short | cut -d' ' -f2` ; do printf "%-25s%-25s" "`date '+%x %X'`" "`dig AAAA $i +short`" ; e=`curl -6 -sSm 5 $i:25 2>&1 >/dev/null`; r=$?; echo "$e $r"; done 05/07/2014 02:18:32 PM 2607:f8b0:400d:c04::1b 0 05/07/2014 02:18:32 PM 2607:f8b0:400c:c01::1b 0 05/07/2014 02:18:33 PM 2607:f8b0:400e:c03::1a 0 05/07/2014 02:18:33 PM 2607:f8b0:4001:c03::1a 0 05/07/2014 02:18:34 PM 2607:f8b0:4002:c01::1a 0 Seems to work OK for me from my home location (2620:0:930::/48 AS1734). Just another datapoint. As Reid mentioned, the folks at support@he.net are in the best position to help you resolve any issues. Owen On May 7, 2014, at 10:18 , Spencer Gaw <spencerg@frii.net> wrote:
Hmmm, looks like you might be on to something. From HE6in4:
root@alpha:~# for i in `dig mx gmail.com +short | cut -d' ' -f2` ; do printf "%-25s%-25s" "`date '+%x %X'`" "`dig AAAA $i +short`" ; e=`curl -6 -sSm 5 $i:25 2>&1 >/dev/null`; r=$?; echo "$e $r" ; done 05/07/2014 11:19:09 AM 2607:f8b0:4002:c01::1b curl: (28) connect() timed out! 28 05/07/2014 11:19:15 AM 2607:f8b0:400e:c03::1a curl: (28) connect() timed out! 28 05/07/2014 11:19:20 AM 2607:f8b0:4001:c03::1a curl: (28) connect() timed out! 28 05/07/2014 11:19:25 AM 2607:f8b0:400d:c04::1a curl: (28) connect() timed out! 28 05/07/2014 11:19:30 AM 2607:f8b0:400c:c01::1a curl: (28) connect() timed out! 28
From native IPv6:
root@test:~# for i in `dig mx gmail.com +short | cut -d' ' -f2` ; do printf "%-25s%-25s" "`date '+%x %X'`" "`dig AAAA $i +short`" ; e=`curl -6 -sSm 5 $i:25 2>&1 >/dev/null`; r=$?; echo "$e $r" ; done 05/07/2014 11:14:29 AM 2607:f8b0:4001:c03::1a 0 05/07/2014 11:14:29 AM 2607:f8b0:400d:c04::1a 0 05/07/2014 11:14:29 AM 2607:f8b0:400c:c01::1a 0 05/07/2014 11:14:30 AM 2a00:1450:400c:c05::1b 0 05/07/2014 11:14:30 AM 2a00:1450:4013:c00::1a 0
No issues with IPv6 web traffic though. Anyone else seeing this?
Regards,
SG
On 5/7/2014 8:32 AM, Joshua M Boniface wrote:
The problem I've been seeing is specifically with service connectivity. I'm on the Toronto, ON tunnel. Pings and traceroutes complete without any problems, however as soon as services (specifically mail-related, IMAP and SMTP) were run across the tunnel, they would time out and fail. I'm just looking to see if anyone else has noticed something similar over the past few days.
On 14-05-07 10:14 AM, Spencer Gaw wrote:
root@alpha:~# traceroute6 ipv6.google.com traceroute to ipv6.google.com (2607:f8b0:4005:802::1002), 30 hops max, 80 byte packets 1 redacted-2.tunnel.tserv1.den1.ipv6.he.net (2001:470:39:223:) 71.129 ms 76.464 ms 76.487 ms 2 ge2-19.core1.den1.he.net (2001:470:0:24b::1) 76.536 ms 80.735 ms 81.544 ms 3 10ge4-3.core1.chi1.he.net (2001:470:0:1af::1) 107.123 ms 107.152 ms 107.186 ms 4 google-as15169.10gigabitethernet7.switch2.chi1.he.net (2001:470:0:bf::2) 107.302 ms 114.789 ms 114.014 ms 5 2001:4860::1:0:92e (2001:4860::1:0:92e) 112.507 ms 112.537 ms 130.409 ms 6 2001:4860::8:0:5900 (2001:4860::8:0:5900) 120.730 ms 2001:4860::8:0:5901 (2001:4860::8:0:5901) 91.607 ms * 7 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 102.758 ms 2001:4860::8:0:64da (2001:4860::8:0:64da) 112.617 ms 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 106.705 ms 8 2001:4860::8:0:3427 (2001:4860::8:0:3427) 116.717 ms 2001:4860::8:0:3426 (2001:4860::8:0:3426) 118.457 ms 2001:4860::8:0:3427 (2001:4860::8:0:3427) 118.777 ms 9 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.603 ms 2001:4860::8:0:2cb6 (2001:4860::8:0:2cb6) 123.749 ms 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.057 ms 10 2001:4860::1:0:7ea (2001:4860::1:0:7ea) 135.940 ms 138.026 ms 137.344 ms 11 2001:4860:0:1::693 (2001:4860:0:1::693) 132.675 ms 134.535 ms 116.313 ms 12 2607:f8b0:4005:802::15 (2607:f8b0:4005:802::15) 118.554 ms 119.782 ms 115.659 ms
Denver endpoint in case it wasn't clear from the traceroute. Could you elaborate on the issues you're seeing?
Regards,
SG
On 5/7/2014 7:27 AM, Joshua M Boniface wrote:
I've been experiencing IPv6 connectivity issues all this week, and had to disable my tunnel completely last night. Anyone experiencing any problems with HE IPv6 tunnels? _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Have you emailed into support@he.net? Reid On Wed, May 7, 2014 at 10:32 AM, Joshua M Boniface <joshua@boniface.me>wrote:
The problem I've been seeing is specifically with service connectivity. I'm on the Toronto, ON tunnel. Pings and traceroutes complete without any problems, however as soon as services (specifically mail-related, IMAP and SMTP) were run across the tunnel, they would time out and fail. I'm just looking to see if anyone else has noticed something similar over the past few days.
On 14-05-07 10:14 AM, Spencer Gaw wrote:
root@alpha:~# traceroute6 ipv6.google.com traceroute to ipv6.google.com (2607:f8b0:4005:802::1002), 30 hops max, 80 byte packets 1 redacted-2.tunnel.tserv1.den1.ipv6.he.net (2001:470:39:223:) 71.129 ms 76.464 ms 76.487 ms 2 ge2-19.core1.den1.he.net (2001:470:0:24b::1) 76.536 ms 80.735 ms 81.544 ms 3 10ge4-3.core1.chi1.he.net (2001:470:0:1af::1) 107.123 ms 107.152 ms 107.186 ms 4 google-as15169.10gigabitethernet7.switch2.chi1.he.net(2001:470:0:bf::2) 107.302 ms 114.789 ms 114.014 ms 5 2001:4860::1:0:92e (2001:4860::1:0:92e) 112.507 ms 112.537 ms 130.409 ms 6 2001:4860::8:0:5900 (2001:4860::8:0:5900) 120.730 ms 2001:4860::8:0:5901 (2001:4860::8:0:5901) 91.607 ms * 7 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 102.758 ms 2001:4860::8:0:64da (2001:4860::8:0:64da) 112.617 ms 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 106.705 ms 8 2001:4860::8:0:3427 (2001:4860::8:0:3427) 116.717 ms 2001:4860::8:0:3426 (2001:4860::8:0:3426) 118.457 ms 2001:4860::8:0:3427 (2001:4860::8:0:3427) 118.777 ms 9 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.603 ms 2001:4860::8:0:2cb6 (2001:4860::8:0:2cb6) 123.749 ms 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.057 ms 10 2001:4860::1:0:7ea (2001:4860::1:0:7ea) 135.940 ms 138.026 ms 137.344 ms 11 2001:4860:0:1::693 (2001:4860:0:1::693) 132.675 ms 134.535 ms 116.313 ms 12 2607:f8b0:4005:802::15 (2607:f8b0:4005:802::15) 118.554 ms 119.782 ms 115.659 ms
Denver endpoint in case it wasn't clear from the traceroute. Could you elaborate on the issues you're seeing?
Regards,
SG
On 5/7/2014 7:27 AM, Joshua M Boniface wrote:
I've been experiencing IPv6 connectivity issues all this week, and had to disable my tunnel completely last night. Anyone experiencing any problems with HE IPv6 tunnels? _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Reid Fishler Director Hurricane Electric +1-510-580-4178
I have, and they're mentioning the MTU discovery as well. I'm following up with them further. On 14-05-07 01:19 PM, Reid Fishler wrote:
Have you emailed into support@he.net <mailto:support@he.net>?
Reid
On Wed, May 7, 2014 at 10:32 AM, Joshua M Boniface <joshua@boniface.me <mailto:joshua@boniface.me>> wrote:
The problem I've been seeing is specifically with service connectivity. I'm on the Toronto, ON tunnel. Pings and traceroutes complete without any problems, however as soon as services (specifically mail-related, IMAP and SMTP) were run across the tunnel, they would time out and fail. I'm just looking to see if anyone else has noticed something similar over the past few days.
On 14-05-07 10:14 AM, Spencer Gaw wrote:
root@alpha:~# traceroute6 ipv6.google.com <http://ipv6.google.com> traceroute to ipv6.google.com <http://ipv6.google.com> (2607:f8b0:4005:802::1002), 30 hops max, 80 byte packets 1 redacted-2.tunnel.tserv1.den1.ipv6.he.net <http://redacted-2.tunnel.tserv1.den1.ipv6.he.net> (2001:470:39:223:) 71.129 ms 76.464 ms 76.487 ms 2 ge2-19.core1.den1.he.net <http://ge2-19.core1.den1.he.net> (2001:470:0:24b::1) 76.536 ms 80.735 ms 81.544 ms 3 10ge4-3.core1.chi1.he.net <http://10ge4-3.core1.chi1.he.net> (2001:470:0:1af::1) 107.123 ms 107.152 ms 107.186 ms 4 google-as15169.10gigabitethernet7.switch2.chi1.he.net <http://google-as15169.10gigabitethernet7.switch2.chi1.he.net> (2001:470:0:bf::2) 107.302 ms 114.789 ms 114.014 ms 5 2001:4860::1:0:92e (2001:4860::1:0:92e) 112.507 ms 112.537 ms 130.409 ms 6 2001:4860::8:0:5900 (2001:4860::8:0:5900) 120.730 ms 2001:4860::8:0:5901 (2001:4860::8:0:5901) 91.607 ms * 7 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 102.758 ms 2001:4860::8:0:64da (2001:4860::8:0:64da) 112.617 ms 2001:4860::8:0:4cde (2001:4860::8:0:4cde) 106.705 ms 8 2001:4860::8:0:3427 (2001:4860::8:0:3427) 116.717 ms 2001:4860::8:0:3426 (2001:4860::8:0:3426) 118.457 ms 2001:4860::8:0:3427 (2001:4860::8:0:3427) 118.777 ms 9 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.603 ms 2001:4860::8:0:2cb6 (2001:4860::8:0:2cb6) 123.749 ms 2001:4860::8:0:6117 (2001:4860::8:0:6117) 125.057 ms 10 2001:4860::1:0:7ea (2001:4860::1:0:7ea) 135.940 ms 138.026 ms 137.344 ms 11 2001:4860:0:1::693 (2001:4860:0:1::693) 132.675 ms 134.535 ms 116.313 ms 12 2607:f8b0:4005:802::15 (2607:f8b0:4005:802::15) 118.554 ms 119.782 ms 115.659 ms
Denver endpoint in case it wasn't clear from the traceroute. Could you elaborate on the issues you're seeing?
Regards,
SG
On 5/7/2014 7:27 AM, Joshua M Boniface wrote:
I've been experiencing IPv6 connectivity issues all this week, and had to disable my tunnel completely last night. Anyone experiencing any problems with HE IPv6 tunnels? _______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
-- Reid Fishler Director Hurricane Electric +1-510-580-4178
Yes, through Dallas in particular...to the point where I finally just disabled it. Tried again a few minutes ago, and the latency is so high and throughput so low that I immediately turned it right back off. Took over a minute to load my Gmail inbox with the tunnel...not sure what the issue is. On Wed, May 7, 2014 at 8:27 AM, Joshua M Boniface <joshua@boniface.me>wrote:
I've been experiencing IPv6 connectivity issues all this week, and had to disable my tunnel completely last night. Anyone experiencing any problems with HE IPv6 tunnels? _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Tunnel Broker = Tunnel BROKEN (at the moment) On Wed, May 7, 2014 at 5:02 PM, Blair Trosper <blair.trosper@gmail.com>wrote:
Yes, through Dallas in particular...to the point where I finally just disabled it. Tried again a few minutes ago, and the latency is so high and throughput so low that I immediately turned it right back off.
Took over a minute to load my Gmail inbox with the tunnel...not sure what the issue is.
On Wed, May 7, 2014 at 8:27 AM, Joshua M Boniface <joshua@boniface.me>wrote:
I've been experiencing IPv6 connectivity issues all this week, and had to disable my tunnel completely last night. Anyone experiencing any problems with HE IPv6 tunnels? _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I don't see any tickets in the queue from you, can you please email in your traceroutes to support@he.net? We would like to try to help you. Reid On Wed, May 7, 2014 at 6:21 PM, Blair Trosper <blair.trosper@gmail.com>wrote:
Tunnel Broker = Tunnel BROKEN (at the moment)
On Wed, May 7, 2014 at 5:02 PM, Blair Trosper <blair.trosper@gmail.com>wrote:
Yes, through Dallas in particular...to the point where I finally just disabled it. Tried again a few minutes ago, and the latency is so high and throughput so low that I immediately turned it right back off.
Took over a minute to load my Gmail inbox with the tunnel...not sure what the issue is.
On Wed, May 7, 2014 at 8:27 AM, Joshua M Boniface <joshua@boniface.me>wrote:
I've been experiencing IPv6 connectivity issues all this week, and had to disable my tunnel completely last night. Anyone experiencing any problems with HE IPv6 tunnels? _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Reid Fishler Director Hurricane Electric +1-510-580-4178
participants (5)
-
Blair Trosper -
Joshua M Boniface -
Owen DeLong -
Reid Fishler -
Spencer Gaw