Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've found a lot of information specifying that this is the case, however, I am really looking for the reason behind this. Why is it necessary? Is it necessary?

share|improve this question
up vote 10 down vote accepted

The DF flag instructs routers who would normally fragment the packet due to it being too large for a link's MTU (and potentially deliver it out of order due to that fragmentation) to instead drop the packet and return an ICMP Fragmentation Needed packet, allowing the sending host to account for the lower MTU on the path to the destination host. This process is called "Path MTU discovery".

It's generally better to leave PMTUD alone and let it do its work, as opposed to having your TCP stack dealing with out of order fragments. However, in some cases (mainly when the necessary ICMP is blocked) the PMTUD doesn't work, and the connection breaks.

That's when you'll want to have the DF flag unset - when PMTUD can't function properly and connection problems result.

share|improve this answer
Is there a reason that encrypted traffic, ie. ssh and https traffic shouldn't be fragmented? – Aiden Thompson Nov 16 '13 at 2:22
@AidenThompson Generally, letting PMTUD do its thing instead of letting fragmentation happen is better for performance for all TCP connections, including SSH and HTTPS. – Shane Madden Nov 16 '13 at 7:18
(I.e., it has nothing to do with encryption, and everything to do with TCP.) – user137177 Nov 16 '13 at 19:49
This is one of those things that server and network worlds will never agree upon. – Smithers May 5 '15 at 14:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.