From: Rafal Jaworowski <raj@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Multicast TFTP problems
Date: Wed, 29 Aug 2007 09:37:36 +0200 [thread overview]
Message-ID: <46D52240.1030209@semihalf.com> (raw)
In-Reply-To: <46CD94A5.8070606@qstreams.com>
Ben Warren wrote:
[...]
> TFTP packets are structured as follows:
>
> | Eth header (14 bytes) | IP header (20 bytes) | UDP header (8 bytes) |
> TFTP message | Eth FCS (4 bytes) |
>
> You can see that the total overhead is 46 bytes. If your network port's
> maximum MTU size is 1500 bytes (the default), the math works out for a
> maximum TFTP PDU size of 1454 bytes.
>
> However... the Ethernet header/trailer is not supposed to be included in
> the MTU. I suspect we have a terminology problem here. Let me dig a bit
> further to find out what's going on.
>
Hi Ben,
Did you manage to look at this any further?
kind regards,
Rafal
next prev parent reply other threads:[~2007-08-29 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 9:41 [U-Boot-Users] Multicast TFTP problems Rafal Jaworowski
2007-08-23 14:07 ` Ben Warren
2007-08-23 14:47 ` David Updegraff
2007-08-29 7:37 ` Rafal Jaworowski [this message]
2007-08-29 15:17 ` Ben Warren
2007-09-05 17:06 ` Rafal Jaworowski
2007-09-05 17:30 ` Ben Warren
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=46D52240.1030209@semihalf.com \
--to=raj@semihalf.com \
--cc=u-boot@lists.denx.de \
/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