<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [U-Boot-Users] [PATCH] DHCP Client Fix</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Ben,<BR>
<BR>
Just a note...one of the ways that I came up with this solution that is presented in this patch was from observing a Fedora Linux machine and an Apple MacBook Pro interact with the same routers because these computers were able to get an IP address through either Linksys DHCP server consistently. There were some differences in the data that was included in each of the DHCP negotiation packets but it was the difference you see in the patch that allowed U-Boot to work with the new firmware. After doing some research on DHCP IP assignments, this seemed like a viable solution according to the spec.<BR>
<BR>
Justin<BR>
<BR>
<BR>
>Wolfgang Denk wrote:<BR>
>>Dear Justin,<BR>
>><BR>
>>in message <4155D0DA4B6B044891B3F19311C7E7B89C45E4@EXCHANGE1.886llc.local> you wrote:<BR>
>> <BR>
>>>I recently upgraded the firmware on some of my old Linksys WRT54G<BR>
>>>routers (version 5) from firmware version 1.0.6 to firmware version<BR>
>>>1.02.2, both of which are released by Linksys and U-Boot was no longer<BR>
>>>able to get an IP address using DHCP. However, with the older firmware<BR>
>>>(version 1.0.6), U-Boot was still able to get an IP through DHCP.<BR>
>>><BR>
>>>Using a hub and a packet sniffer, I was able to locate the problem. The<BR>
>>>U-Boot code will bind to an IP address offered by the DHCP server<BR>
>>>prematurely and the DHCP server will not respond with an ACK, rendering<BR>
>>> <BR>
>><BR>
>>I have to admit that I'm not sure if this is a bug in U-Boot or in<BR>
>>the Linksys router (which I have under special observation as they<BR>
>>explicitely and intentionally violate the U-Boot GPL).<BR>
>><BR>
>><BR>
>>>the system without an IP address. This is no longer valid when using a<BR>
>>>Linksys router as DHCP server. I modified the code to operate the way<BR>
>>>the Linux DHCP client does by not binding to the offered IP until the<BR>
>>>DHCP client receives the ACK sent by the server, ending the<BR>
>>>conversation. After making the appropriate changes, DCHP service was<BR>
>>>restored for all flavors of the Linksys firmware that I have available<BR>
>>>(v 1.02.2 and v1.0.6 for the version 5 router, v8.00.2 for the version 8<BR>
>>>router). It has also been tested on an AirPort Extreme router running<BR>
>>>DHCP.<BR>
>>><BR>
>>>Attached is the patch with the code changes that were made. Any feed<BR>
>>>back would be appreciated.<BR>
>>> <BR>
>>><BR>
>><BR>
>>I'm waiting for feedback (or a pull request?) from the network<BR>
>>custodian.<BR>
>><BR>
>>Ben???<BR>
>><BR>
>><BR>
>This looks promising. I'll provide feedback after doing some testing tomorrow.<BR>
><BR>
>regards,<BR>
>Ben </FONT>
</P>
</BODY>
</HTML>