From: Rafal Jaworowski <raj@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Multicast TFTP problems
Date: Wed, 05 Sep 2007 19:06:23 +0200 [thread overview]
Message-ID: <46DEE20F.2090702@semihalf.com> (raw)
In-Reply-To: <46D58DF8.3020209@qstreams.com>
Ben Warren wrote:
> The size of 1468 works fine for me on an MPC8349EMDS board. I captured
> the transfer using Wireshark (Ethereal) and the numbers match exactly as
> I've shown above.
> Here are the first few transfers.
>
[...]
>
> The only thing I can think of is that something on your network is
> limiting the MTU size to less than 1500 bytes. Are you using VLANs or
> PPPoE? Maybe your server has its MTU limited to 1486?
>
Hi Ben,
Thanks for your help. It turned there was a bug in the MPC5121 FEC
driver which occured only upon some bigger frames, so it wasn't anything
MTU-related or the TFTP code. Strangely enough, the frame size offset it
would or not corrupt coincided with the 46 bytes that are overhead for
the TFTP...
kind regards,
Rafal
next prev parent reply other threads:[~2007-09-05 17:06 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
2007-08-29 15:17 ` Ben Warren
2007-09-05 17:06 ` Rafal Jaworowski [this message]
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=46DEE20F.2090702@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