Description of Problem: DHCP doesn't serve BOOTP clients correctly Version-Release number of selected component (if applicable): RH72-alpha-beta2 How Reproducible: Always. Steps to Reproduce: 1. configure DHCP to serve BOOTP clients (see sample config attached) 2. observe DHCP logging BOOTREQUESTs and BOOTREPLY messages 3. observe client not receiving BOOTREPLY message Actual Results: client never appears to receive the BOOTREPLY message that the server is supposed to send out. Expected Results: client should receive a message indicating various information about how it is supposed to proceed. Additional Information: TFTP is configured and working, as I can bypass the DHCP server and go directly to TFTP from a client and receive the desired file. NOTE: the 7.2 x86 version of DHCP seems to have the same problem, so either both are broken or there's something I don't understand about how this is supposed to work.
Created attachment 51688 [details] sample /etc/dhcpd.conf file as used for testing
Rebuilt and replaced /usr/sbin/dhcp from the dhcp-2.0p15-8.src.rpm via: ./configure make cp server/dhcpd /usr/sbin Had to do: mkdir -p /var/state/dhcp touch /var/state/dhcp/dhcpd.leases It then immediately started serving requests correctly. Perhaps the binary RPM has an older or mis-configured server in it?
OK; I tracked it down to the args used to invoke "./configure' with. If you don't leave the first argument null (via "", I think), it won't get the Linux major/minor version info correct, and this will lead to a mis-configure of the server (at least), because of dependency on the symbol LINUX_MAJOR in includes/cf/linux.h. It looks as if it might be easier to patch "configure" rather than figure out a way to pass a null first arg... ;-}
Ok,.. I'm looking at dhcpd-1.3.22pl1-7 I've built an rpm that I want throw your way as I don't have a suitable enviroment here to test this with. (Elliot, I've had to add automake and a "" to %configure in the spec file to get this to compile on the alpha.) Phil =--=
Created attachment 54264 [details] Binary dhcpd to test
Wel, no news is good news,.. I'm out of time so this is going in as fixed for the next cycle. Elliot be advised that this is being flagged as a generic bug Phil =--=