by
tomoc » Fri Jan 20, 2017 9:25 am
Apologies for the late reply, I have at least a couple answers for you.
nsmiller wrote:I have a 6rd tunnel. I usually pass test-ipv6.com 10/10. Nevertheless, when accessing ssa.gov, I have to disable IPv6 to use the site; else the site chokes on a login attempt.
From my initial research, this looks to be an IPv6 issue well outside our network. I picked a random only IPv6 traceroute utility and am having the same reachability issues. (I used
http://www.subnetonline.com/pages/ipv6- ... eroute.php to try and trace to ssa.gov)
nsmiller wrote: And when I try to access mail.yahoo.com, Opera, SeaMonkey, and IE12 Spin and spin, then fail. Opera throws this message:
This site can’t be reached
mail.yahoo.com took too long to respond.
Yet disable IPv6, and I have no problem accessing, or logging in.
I don't see a problem with this from a traceroute standpoint, so I'll have to take a look and see what I can find in our lab with a 6rd connection-- I'll get back to you
nsmiller wrote:Next idea is to test the 6in4 tunnel, and to resurrect my Hurricane Electric 6in4 tunnel to see of one of those works.
I'm curious if this works, but fixing 6rd needs to happen anyway
wwwdrich wrote:I'm seeing very odd things with traceroute as well. As an example, I can ping my server at home from an external host just fine, but a traceroute to that same system fails on one of Sonic's devices.
Code: Select all
> ping6 2602:243:2002:7f30:4000::20
PING6(56=40+8+8 bytes) 2001:1868:a000:17::142 --> 2602:243:2002:7f30:4000::20
16 bytes from 2602:243:2002:7f30:4000::20, icmp_seq=0 hlim=56 time=28.133 ms
16 bytes from 2602:243:2002:7f30:4000::20, icmp_seq=1 hlim=56 time=27.709 ms
16 bytes from 2602:243:2002:7f30:4000::20, icmp_seq=2 hlim=56 time=20.611 ms
16 bytes from 2602:243:2002:7f30:4000::20, icmp_seq=3 hlim=56 time=24.598 ms
16 bytes from 2602:243:2002:7f30:4000::20, icmp_seq=4 hlim=56 time=32.279 ms
^C
--- 2602:243:2002:7f30:4000::20 ping6 statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 20.611/26.666/32.279/3.891 ms
> traceroute6 2602:243:2002:7f30:4000::20
traceroute6 to 2602:243:2002:7f30:4000::20 (2602:243:2002:7f30:4000::20) from 2001:1868:a000:17::142, 64 hops max, 12 byte packets
1 2001:1868:a000:17::1 0.621 ms 6.319 ms 0.624 ms
2 xe0-0-0-4.core3.scl.layer42.net 1.041 ms 0.587 ms 0.542 ms
3 xe0-0-0-0-100.core1.sv8.layer42.net 1.267 ms 0.941 ms 0.901 ms
4 2001:1868:a200::2 2.428 ms 1.888 ms 1.756 ms
5 0.xe-6-0-0.gw.equinix-sj.sonic.net 1.341 ms 1.099 ms 1.081 ms
6 201.ge-1-2-0.cgn-gw.equinix-sj.sonic.net 1.191 ms 1.390 ms 1.160 ms
7 * * *
8 * * *
^C
The last hop you are seeing in that traceroute is the IPv6 endpoint where your traffic gets re-encapsulated and hauled over our IPv4 network. I confess I am not sure whether your 6rd endpoint (modem/router) should be responding to traceroute traffic, but I would not be the least bit surprised if not.