no DHCPREQUEST after DHCPOFFER
hwang at circadiant.com
Tue May 30 17:46:23 UTC 2006
Very appreciate your help.
I think on the dynamic case( Non working version ), the client does not send
DHCPREQUEST due to the DHCPOFFER it got does now totally meet the requirement. in this case, the client is etherboot. (rom 5.16), after I have
installed the linux, the linux is able to get ip from the same server and
same config (both dynamic and manual ) using the same ethernet port.
looked like in the manual config case, the mac address of the client has
been sent to etherboot while in the dynamic case, it's not.
my question is then:
1.is it true ?
2. if it is true, then how do I config the dhcpd server to send MAC
address of the client in the DHCPOFFER in the dynamic config case ?
AT this point I need to correct something. You talk of "the server is
able to get the DHCPREQUEST" as though this is something the server
does. The server is passive in this, if the client sends it, the
server will get it, if the client doesn't send it, there's nothing
you can do at the server end to fix this - apart from ...
figure out why the client is not accepting the offer.
Firstly, look carefully at your server config, and see if the options
send when specifying a fixed address are in any way different to
those sent when using a dynamic address. You could post your config
file here and we can take a look.
Next, you could look at the packets on the wire and see what is sent
out - compare the offer packets for the two cases and see what's
different. With ethereal installed, 'tethereal -V -f "ether host
aa:bb:cc:dd:ee:ff and (port 67 or port 68)"' should do it.
The only explanation I can see is that in the two cases, the offer
packet differ in more than just than IP address and the client is not
happy with one of them.
More information about the dhcp-users