From: Glen Turner <gdt@gdt.id.au>
To: netdev@vger.kernel.org
Subject: DF Bit set on UDP traffic -- bug or feature?
Date: Thu, 20 Aug 2009 09:22:45 +1000 [thread overview]
Message-ID: <4A8C8945.70602@gdt.id.au> (raw)
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
next reply other threads:[~2009-08-20 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 23:22 Glen Turner [this message]
2009-08-20 4:16 ` DF Bit set on UDP traffic -- bug or feature? David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A8C8945.70602@gdt.id.au \
--to=gdt@gdt.id.au \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).