4 ms·
Sorry you're right the default stacks do set DF on v4, my bad. Otherwise they wouldn't be able to get the PMTUD message so they know to change MSS as when fragm
by zamadatix 6y ago
Sorry you're right the default stacks do set DF on v4, my bad. Otherwise they wouldn't be able to get the PMTUD message so they know to change MSS as when fragmentation is enabled v4 won't send PMTUD ICMP back (and PMTUD working out of the box most of the time is preferred to fragmentation all the time). Had that backwards in my head.
Yeah no stacks do it that I know of, just a theoretical way one could without having to rely on in-path devices sending messages or dropping traffic. I think the v6 path of drop it and send it back was better though. If it's blocked that's their fault :p.
Regarding sending the "message too long" note via in band channel instead of its own ICMP message I actually think that's a great angle as it'll get through more FWs I'm just hung up on trying to do something the truncated payload once it arrives... but I guess that doesn't really matter from a protocol perspective - the important bit is the note on the MTU issue arrive in band and the OS can decide what to do with any remaining payload for inner protocols after that as it's not IP's problem. v6 already got rid of the IP checksum so the only other things that might need to be updated are NICs/FWs/NAT boxes that check TCP/UDP/protocol checksums to ignore them if the header had that note.