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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A8C8945.70602@gdt.id.au>
Date:	Thu, 20 Aug 2009 09:22:45 +1000
From:	Glen Turner <gdt@....id.au>
To:	netdev@...r.kernel.org
Subject: DF Bit set on UDP traffic -- bug or feature?

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html