DF Bit set on UDP traffic -- bug or feature?

DF Bit set on UDP traffic -- bug or feature?

[Glen Turner]

Hi folks,

Is it a bug that the DF bit is set on UDP traffic when TCP Path
MTU Discovery is active, but yet when a returning ICMP DF Set But
Fragmentation Required response is received the kernel does not
attempt fragmentation of the outgoing UDP-carrying IP packets?

This has practical consequences for large RADIUS packets, such
as in the RADIUS/TLS/UDP protocol "DTLS".  They are not fragmented
by the network and they are not fragmented by the kernel, and thus
the packets fail to pass from the application to the end-user.

Can I humbly suggest that when the kernel does not implement
its own fragmentation strategy (as it does with TCP Path MTU
Discovery) that the DF bit not be set by the kernel?

Thanks very much, Glen

-- 
  Glen Turner, Network Engineer, Australia's Academic & Research Network
  www.aarnet.edu.au
  +61 8 8303 3936

Re: DF Bit set on UDP traffic -- bug or feature?

[David Miller]

From: Glen Turner <gdt@gdt.id.au>
Date: Thu, 20 Aug 2009 09:22:45 +1000

> Can I humbly suggest that when the kernel does not implement
> its own fragmentation strategy (as it does with TCP Path MTU
> Discovery) that the DF bit not be set by the kernel?

It's UDP path MTU discovery, it's legal, and Linux has been
doing it for almost 10 years.

I don't think it's changing, sorry.