5 ms·
No comments on history, AFAIK, Packet Length Limit: 1500 was found on a stone tablet. But note that many high profile sites purposefully do not send 1500 byte
by toast0 5y ago
No comments on history, AFAIK, Packet Length Limit: 1500 was found on a stone tablet.
But note that many high profile sites purposefully do not send 1500 byte packets. Path MTU detection has many cases where it doesn't work, so it's simpler to say f*** it and set your effective MTU to 1450 or 1480 and call it a day.
Reflecting the MSS in SYN minus 8 (assuming a poorly configured PPPoE link) or 20 (assuming a poorly configured IPIP tunnel) or even 28 (both) is probably more effective, but stats are hard to gather, and AFAIK no OS makes it easy to run a test, you'd need to patch things and divert packets and have a good representative section of users, etc.
- zamadatix 5y agoby made it a bit easier: assume 1280 unless pmtud is able to show otherwise. V4 had something similar with 576 but it was a bit too small to just default to and started out before pmtud was settled so couldn't mandate it
- rubatuga 5y agoYep 1280 is the minimum for IPv6. Cloudflare used to do 1280, but then they said good riddance and increased it (for better efficiency) https://blog.cloudflare.com/increasing-ipv6-mtu/ https://blog.cloudflare.com/increasing-ipv6-mtu/
- zamadatix 5y ago"by"=what my phone thinks IPv6 should be.
- rjsw 5y agoSome of that is down to the PPPoE standards. I added RFC4638 support to the OS that I use but don't know how ISPs that don't support it will respond.
- netr0ute 5y agoI'd expect those ISPs to use jumbo frames only where they use PPPoE so that it looks "transparent" to non-PPPoE traffic.
- deleted 5y ago[deleted]
- rjsw 5y agoThat is the whole point of RFC4638, it allows you to request an MTU of 1508 for the PPPoE connection so that the tunnelled frames can be 1500 bytes. The problem is that it tries to be backwards compatible which makes it hard to deal with this request not getting granted.
- bcrl 5y agoI've tried to detect MTU on PPPoE sessions with LCP echo requests, and it works... Until I came across consumer wireless routers that send back short LCP echo replies to 1500 byte LCP echo requests. Sometimes software is such complete garbage in the real world.
- toast0 5y agoWell yeah, PPPoE is super derpy; but at least the modems could be trained to adjust MSS on the way in and out to (tcp) 1472, but they often don't, and sometimes only adjust mss on the way out, not on the way in. My current PPPoE ISP doesn't support RFC4638, and my previous ISP was worse, I had a fiber connection with 1500 MTU, but their 6rd gateway was only 1492 MTU (so ipv6 MTU was 1472 after the tunnel) and ICMP needs frag was rate limited, so IPv6 would only sometimes work until I figured out I needed to adjust the v6 MTU. Did you know Windows doesn't request (or process) MTU information on v4 DHCP? That's a nice touch.
- philjohn 5y agoAnd without dedicated packet processing chips it's a nightmare on anything >= 1Gbps