From Bugzilla Helper: User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.18 i686) When the dhcp server returns certain unknows options (these support Etherboot, see http://etherboot.sourceforge.net/ ) then dhcpcd becomes confused and is not able to get a lease. A packet trace shows that dhcpcd becomes extremely confused, sending very strange packets to dhcpd. Traces are available. Reproducible: Always Steps to Reproduce: 1. set dhcpd to emit the DHCP codes used by etherboot: 128, 129, 160, 184-189 and 192-195 in our case 2. dhcpcd does not work on Wolverine (and earlier releases) 3. remove the DHCP options above and dhcpcd works ok Actual Results: No DHCP lease obtained by client Expected Results: A DHCP lease should have been obtained No other client on our network (about 2000 nodes) display this problem, this only impacts RedHat linux. It may be possible to work around this problem by using the vendor-id so that RedHat clients do not see these options though.
Sorry - it is pump that misbehaves, actually dhcpcd works fine. Pump though is broken as described, it can not handle unknown dhcp options.
Sorry for the unresponsiveness of the previous pump packager... dhcpcd replaces pump for the main system usage in Rawhide, while pump is still used in the installer. Does this bug matter at install time, or is it safe to consider it resolved?
It will also crash pump during install. That is why I use a static address when installing over the network. Pump is not able to handle unknown DHCP options under any circumstances.