google path mtu?
mjl at luckie.org.nz
Fri Jan 23 04:08:14 CET 2015
The path MTU is available to applications. It seems like a bug in
QUIC or Chrome to not send smaller packets when it can know the packets
will be fragmented. Or just use TCP.
On Fri, Jan 23, 2015 at 11:55:57AM +0900, Lorenzo Colitti wrote:
> Thanks for reporting this. What was the effect? Connections just getting stuck?
> Was there fallback to IPv4?
> Personally I don't understand why everyone behind a manually-configured tunnel
> doesn't set the MTU in the RA to the MTU of the tunnel... but that's not an
> excuse for things not working.
> On Fri, Jan 23, 2015 at 11:45 AM, Mikael Abrahamsson <swmike at swm.pp.se> wrote:
> I had another problem with Youtube just now, with Chrome+OSX. I saw my
> machine sending fragmented UDP-packets to google on 443, which it was not
> getting any responses to. On a hunch, I disabled QUIC in Chrome which made
> things start working again.
> 03:20:45.891286 IP6 2001:470:X > 2a02:808:1:100::c: frag (0|1232) 59430 >
> 443: UDP, length 1350
> 03:20:45.891286 IP6 2001:470:X > 2a02:808:1:100::c: frag (1232|126)
> Mikael AbrahamssonÂ Â email: swmike at swm.pp.se
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 181 bytes
Desc: not available
Url : http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20150122/d25451de/attachment.bin
More information about the ipv6-ops