public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Aras Vaichas <arasv@magellan-technology.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] dhcp problems with Windows Server
Date: Wed, 11 Oct 2006 15:38:32 +1000	[thread overview]
Message-ID: <452C8358.40009@magellan-technology.com> (raw)
In-Reply-To: <452C3EEA.9010202@magellan-technology.com>

Aras Vaichas wrote:
> Hello,
> 
> I'm seeing problems with the DHCP mechanism in U-Boot and the DHCP server on
> Windows Server 2000/2003. We use U-Boot 1.2 on an at91rm9200 based platform
> with the DM9161 PHY.
> 
> Now I understand that this may not be a U-Boot problem, but for the sake of
> interoperability it may be a good idea to try and fix it as many people use
> Windows Server ...
> 
> Normally we use Un*x DHCP servers and I get 100% success rate but with the
> Microsoft version of DHCP I see about a 75% success rate. i.e. 1 in 4 requests
> will fail.
> 
> Looking at the packets with Ethereal, it looks like the DHCP server isn't
> sending the final "DHCP ACK" for the "DHCP Request" from the U-Boot. Something
> that U-Boot is sending in the "DHCP Request" to the Windows Server is causing
> it to fail occasionally.

Sorry to answer my own question, but I've found the problem and a solution.

The problem appears to be that Windows Server is occasionally too slow to be
able to process the DHCP request. If the time between Windows Server sending
the "DHCP Offer" and U-Boot sending the "DHCP Request" is too short, the
Microsoft DHCP server fails to send the DHCP ACK.

I discovered this when I compiled debugging in to net/bootp.c and I proved it
when I delayed the "DHCP Request" by a small amount (using a printf).

e.g. a DHCP discovery request

U-Boot:	DHCP Discover?
Windows Server DHCP server: DHCP Offer = a.b.c.d
** insert small delay here **
U-Boot: DHCP Request = a.b.c.d?
Windows Server DHCP server: DHCP ACK

I'm not sure what the actual delay should be and I'm not sure where it should
go. Wolfgang, can you suggest a place to put a delay, and should it be wrapped
in a CONFIG_ option?



regards,

Aras Vaichas

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

  reply	other threads:[~2006-10-11  5:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11  0:46 [U-Boot-Users] dhcp problems with Windows Server Aras Vaichas
2006-10-11  5:38 ` Aras Vaichas [this message]
2006-10-11  7:31   ` Wolfgang Denk
2006-10-11 23:46     ` Aras Vaichas
2006-10-12  0:09       ` Wolfgang Denk
2006-10-11  6:47 ` Wolfgang Denk

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=452C8358.40009@magellan-technology.com \
    --to=arasv@magellan-technology.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