Print

[gnarlymarley]

I am not sure the MTU is the problem on all data centers.  I see you have 2a00:1450:4000::/40, which that range works for me when I use a hosts file.  I also have a few other ranges that work for me.  I did a search for the google ipv6 hosts file from years ago and found some such as https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uact=8&ved=0CCQQFjAB&url=http%3A%2F%2Fcode.google.com%2Fp%2Fipv6-hosts%2Fissues%2FattachmentText%3Fid%3D171%26aid%3D1710002001%26name%3DHost%2BFile%2528small%2529.txt%26token%3D9I1bwXv4-w0qtlXh2gNlw1X-BJ4%253A1325270539024&ei=xnO9VLfHOIWB8gXQpoLACw&usg=AFQjCNGzLfgvvu3dySWHohdac34NukvBaQ[/img] and it solved my problem with a MTU of both 1280 and 1480.  I sure wish google would fix their network, or else point their CDN buggy DNS to another working data center.

Working Google ranges:
2a00:1450:4000::/40
2404:6800:4000::/40
2800:3f0:4000::/40
2001:4860::/32

Not so working google ranges:
2607:f8b0:4000::/40

EDIT: of course, I only grabbed the youtube.com, gstatic.com, googleapis.com, and google.com domains from that host file to put into mine.

[gnarlymarley]

The irritating issue is that because a the first packet comes back, happy eyeballs does not attempt IPv4.  Probably something we all need to keep in mind as even dual stack hosts can appear IPv6 only on situations like this.

[gnarlymarley]

an FYI to all, it appears to be fixed.  I am not sure how or when, but I routing packets to 2607:f8b0:4000::/40 just fine.  I have yanked my hosts file and all appears to be good.  Can someone else verify?

[terrapin]

Seems to be fixed here as well with the tunnel MTU set to 1480.

[devicenull]

Fixed here as well!

[gnarlymarley]

It appears that the issue might be back again.  Issue is mostly intermittent.

Code: [Select]

>ping google.com

Pinging google.com [2607:f8b0:4000:80b::2000] from 2001:470:8747:1705:5403:aa13:
ae6a:96fa with 32 bytes of data:
Reply from 2607:f8b0:4000:80b::2000: time=104ms
Reply from 2607:f8b0:4000:80b::2000: time=105ms
Reply from 2607:f8b0:4000:80b::2000: time=106ms
Reply from 2607:f8b0:4000:80b::2000: time=106ms

Ping statistics for 2607:f8b0:4000:80b::2000:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 104ms, Maximum = 106ms, Average = 105ms

>ping -l 1440 google.com

Pinging google.com [2607:f8b0:4000:80b::2000] from 2001:470:8747:1705:5403:aa13:
ae6a:96fa with 1440 bytes of data:
General failure.

Ping statistics for 2607:f8b0:4000:80b::2000:
    Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Control-C
^C
>ping -l 1340 google.com

Pinging google.com [2607:f8b0:4000:80b::2000] from 2001:470:8747:1705:5403:aa13:
ae6a:96fa with 1340 bytes of data:
Reply from 2607:f8b0:4000:80b::2000: time=185ms
Reply from 2607:f8b0:4000:80b::2000: time=165ms

Ping statistics for 2607:f8b0:4000:80b::2000:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 165ms, Maximum = 185ms, Average = 175ms
Control-C
^C
>