Incompatibility isc dhcpd 3.0.3 and etherboot 5.4.0 (Solution of several threads!)

Hello,

like in these threads:

Problem with isc-dhcp3-server and etherboot
Problem booting e1000 card : No IP address

I also got the "No IP address" when using an etherboot 5.4.0 image with
isc dhcpd 3.0.3. Same configuration works seameless with isc dhcpd
3.0.2 and etherboot 5.4.0 as well as isc dhcpd 3.0.3 and other dhcpd
clients.

Dumping the the tcp connection (sorry, can't access the dump right now,
if neccessary I will post it later) I found an important difference: th
working message contained the server ip at DHCPDOFFER offset 0x14, but
the failing message contained 0x00 there.

This lead me to the changelog of isc dhcpd 3.0.3:

| Changes since 3.0.2
|
| - The siaddr field was being improperly set to the server-|identifier
when
|   responding to DHCP messages.  RFC2131 clarified the siaddr field as
|   meaning the 'next server in the bootstrap process', eg a tftp
server.
|   The siaddr field is now left zeroed unless next-server is
configured.

So I set "next server" and all worked well with isc dhcpd 3.0.3 and
etherboot 5.4.0.

But if I understand the meaning of this field correctly, it should point
to the tftp server and should not be used in the dhcp process.

Lacking detailed knowledge of the dhcp protocol specification I don't
know which behaviour (filling siaddr or not) is correct. But I'm sure
knowing the exact problem will lead to a fast solution.

bye Max




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf