I've been having issues w/ google IPv6 (more-or-less all services operating over 80/443 have been really bad, though imap/993 has had issues also) for at least 18 hours from a SixXS tunnel which terminates in Ashburn. Coming from 2001:4830:167b:: and generally getting 2607:f8b0:4006:80a::1007 or other things in 2607:f8b0:4002::, 2607:f8b0:4004::, or 2607:f8b0:4006:: No issues w/ other IPv6 traffic. * Joe Hamelin via Outages (outages@outages.org) wrote:

Yep, turning off IPv6 brought Talk back. Note that this is also on an HE tunnel.

-- Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474

On Fri, Nov 7, 2014 at 6:08 PM, Joe Hamelin <joe@nethead.com> wrote:

...

I've been having issues with Google talk today on machines with IPv6 too. No deep testing done, been too busy at the paying job.

-- Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474

On Fri, Nov 7, 2014 at 3:17 PM, Aaron C. de Bruyn via Outages < outages@outages.org> wrote:

...

First request returns a 404.

15:09:16 [aaron@ender:~] $ time wget http://fonts.gstatic.com/s/robotocondensed/v12/b9QBgL0iMZfDSpmcXcE8nBFu3zqwM... --2014-11-07 15:09:21-- http://fonts.gstatic.com/s/robotocondensed/v12/b9QBgL0iMZfDSpmcXcE8nBFu3zqwM... Resolving fonts.gstatic.com (fonts.gstatic.com)... 2607:f8b0:400a:802::101f, 173.194.33.88, 173.194.33.79, ... Connecting to fonts.gstatic.com (font1s.gstatic.com)|2607:f8b0:400a:802::101f|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2014-11-07 15:09:21 ERROR 404: Not Found.

real 0m0.193s user 0m0.003s sys 0m0.004s

Second request connects, in this sample I CTRL+C after 15 seconds. In my browser it times out after about 5 minutes.

15:09:21 [aaron@ender:~] 8 $ time wget http://fonts.gstatic.com/s/robotocondensed/v12/b9QBgL0iMZfDSpmcXcE8nBFu3zqwM... --2014-11-07 15:09:28-- http://fonts.gstatic.com/s/robotocondensed/v12/b9QBgL0iMZfDSpmcXcE8nBFu3zqwM... Resolving fonts.gstatic.com (fonts.gstatic.com)... 2607:f8b0:400a:802::101f, 173.194.33.87, 173.194.33.88, ... Connecting to fonts.gstatic.com (fonts.gstatic.com)|2607:f8b0:400a:802::101f|:80... connected. HTTP request sent, awaiting response... ^C

real 0m15.056s user 0m0.003s sys 0m0.004s

15:09:43 [aaron@ender:~] 130 $

Over IPv4 I occasionally get 404s and other times I get served the content.

It's been happening all day from 208.70.50.0/24.

-A

_______________________________________________ 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

Nice work Mark! It only started for me about a week ago. I've had my HE tunnel for years. I wonder if they just enabled IPv6 service to that particular web property, or if they made a recent config change. Anyways, I wonder if someone from Google reads the outages list, or if NANOG should be CC'd to get their attention. On Sat, Nov 8, 2014 at 11:26 AM, Mark Kamichoff via Outages < outages@outages.org> wrote:

On Sat, Nov 08, 2014 at 08:07:56AM -0500, Stephen Frost via Outages wrote:

...

I've been having issues w/ google IPv6 (more-or-less all services operating over 80/443 have been really bad, though imap/993 has had issues also) for at least 18 hours from a SixXS tunnel which terminates in Ashburn.

"me too" (I'm in Seattle, USA)

I've narrowed down this issue to Google ignoring ICMPv6 PTBs. It sometimes works sporadically for me, though. Here's an example w/some tcpdumps:

http://www.prolixium.com/share/txt/google-ipv6-pmtud-fail.txt

Relevant lines are the following:

13:51:34.046171 IP6 2001:48c8:1:2::2 > 2607:f8b0:4005:802::1006: ICMP6, packet too big, mtu 1280, length 1240 13:51:34.562579 IP6 2607:f8b0:4005:802::1006.443 > 2001:48c8:1:105:21c:c0ff:feb2:8dbd.33936: Flags [.], seq 1:1429, ack 279, win 232, options [nop,nop,TS val 3392471676 ecr 756572814], length 1428

Google never lowers the packet length and so the connection times out. As others have mentioned, this only really affects tunneled users.

I've seen other organizations break this over the years but I never thought Google would make the list..

- Mark

-- Mark Kamichoff prox@prolixium.com http://www.prolixium.com/

_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

On Nov 8, 2014, at 2:26 PM, Mark Kamichoff via Outages <outages@outages.org> wrote:

On Sat, Nov 08, 2014 at 08:07:56AM -0500, Stephen Frost via Outages wrote:

...

I've been having issues w/ google IPv6 (more-or-less all services operating over 80/443 have been really bad, though imap/993 has had issues also) for at least 18 hours from a SixXS tunnel which terminates in Ashburn.

"me too" (I'm in Seattle, USA)

Me three.

I've narrowed down this issue to Google ignoring ICMPv6 PTBs.

Thanks for looking into this, it started affecting me (HE tunnel out of NYC) yesterday, but I didnt have time to nail down what was going on - just disabled v6 on the box I was working on so I could continue to use Google search. Charles

It sometimes works sporadically for me, though. Here's an example w/some tcpdumps:

http://www.prolixium.com/share/txt/google-ipv6-pmtud-fail.txt

Relevant lines are the following:

13:51:34.046171 IP6 2001:48c8:1:2::2 > 2607:f8b0:4005:802::1006: ICMP6, packet too big, mtu 1280, length 1240 13:51:34.562579 IP6 2607:f8b0:4005:802::1006.443 > 2001:48c8:1:105:21c:c0ff:feb2:8dbd.33936: Flags [.], seq 1:1429, ack 279, win 232, options [nop,nop,TS val 3392471676 ecr 756572814], length 1428

Google never lowers the packet length and so the connection times out. As others have mentioned, this only really affects tunneled users.

I've seen other organizations break this over the years but I never thought Google would make the list..

- Mark

-- Mark Kamichoff prox@prolixium.com http://www.prolixium.com/ _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages