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 10:46:34 +1000 [thread overview]
Message-ID: <452C3EEA.9010202@magellan-technology.com> (raw)
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.
As a comparison, I used udhcpc from Busybox to make the DHCP request and I get
a 100% success rate.
There are some obvious differences between the requests from the two pieces of
software. (my test Windows Server 2003 DHCP server is on 10.1.1.1 and is
offering 10.1.1.2). As I am not a low level DHCP packet expert, perhaps someone
else can make sense of this. I will also start studying the BOOTP options
fields and try and understand if any of the U-Boot DHCP packet options are
incorrect.
** U-Boot DHCP sequence **
DHCP Discover:
Seconds Elapsed = 1
Your (client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 0.0.0.0 (0.0.0.0)
Option 53: DHCP Message Type = Discover
Option 57: Maximum DHCP Message Size = 576
Option 55: Parameter Request List
1 = Subnet Mask
3 = Router
12 = Host name
17 = Root Path
DHCP Request:
Seconds Elapsed = 1
Your (client) IP address: 10.1.1.2 (10.1.1.2)
Next server IP address: 10.1.1.1 (10.1.1.1)
Option 53: DHCP Message Type = DHCP Request
Option 57: Maximum DHCP Message Size = 576
Option 54: Server Identifier = 10.1.1.1
Option 50: Requested IP Address = 10.1.1.2
Option 55: Parameter Request List
1 = Subnet Mask
3 = Router
12 = Host name
17 = Root Path
** udhcpc DHCP sequence **
DHCP Discover:
Seconds Elapsed = 0
Your (client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 0.0.0.0 (0.0.0.0)
Option 53: DHCP Message Type = DHCP Discover
Option 61: Client Identifier
Hardware type: Ethernet
Client MAC address: ...
Option 60: Vendor class identifier = "udhcp 0.9.9-pre"
Option 55: Parameter Request List
1 = Subnet Mask
3 = Router
6 = Domain Name Server
12 = Host Name
15 = Domain Name
28 = Broadcast Address
40 = Network Information Service Domain
41 = Network Information Service Servers
42 = Network Time Protocol Servers
DHCP Request:
Seconds Elapsed = 0
Your (client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 0.0.0.0 (0.0.0.0)
Option 53: DHCP Message Type = DHCP Request
Option 61: Client Identifier
Hardware type: Ethernet
Client MAC address: ...
Option 60: Vendor class identifier = "udhcp 0.9.9-pre"
Option 50: Requested IP Address = 10.1.1.2
Option 54: Server Identifier = 10.1.1.1
Option 55: Parameter Request List
1 = Subnet Mask
3 = Router
6 = Domain Name Server
12 = Host Name
15 = Domain Name
28 = Broadcast Address
40 = Network Information Service Domain
41 = Network Information Service Servers
42 = Network Time Protocol Servers
regards,
Aras Vaichas
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
next reply other threads:[~2006-10-11 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 0:46 Aras Vaichas [this message]
2006-10-11 5:38 ` [U-Boot-Users] dhcp problems with Windows Server Aras Vaichas
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=452C3EEA.9010202@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