3 ms·
Interesting! Semi-related problem I dealt with recently: Google Cloud seems to choose a different magic number of 1460 for their VPCs default MTU, which is ann
by parhamn 2y ago
Interesting!
Semi-related problem I dealt with recently: Google Cloud seems to choose a different magic number of 1460 for their VPCs default MTU, which is annoying if you don't know because its different than the default of everything else (such as docker) will cause random packet drops if you do a standard install of those tools.
Took me a few hours to figure this out.
- edward28 2y agoThey must be encapsulating traffic on the backend.
- jppittma 2y agoThere is almost certainly so much network virtualization going on your head would spin.
- londons_explore 2y agoIn the world of ethernet jumbo frames, you'd imagine they could encapsulate the traffic yet still support sensible MTU's...
- derekp7 2y agoI recall working on a customer host that I was ssh'd into. If I did an operation that displayed a bunch of text, the session would freeze up. It wouldn't freeze if I only did a bit of text at at time though. On a whim, I tried lowering the MTU, set it to something like 1000 and it worked without freezing on me. Was able to raise it to 1460 (I believe) and still work, but anything beyond that I would get the session lockups on more than a few sceens of data. Later I researched it, and they were blocking all of ICMP which not only killed ping, but messed with mtu path discovery. Found some information about it on a Cloudflare blog: https://blog.cloudflare.com/path-mtu-discovery-in-practice https://blog.cloudflare.com/path-mtu-discovery-in-practice