Bug 29084

Summary:	dhcpcd completely confused by unknown options sent by dhcpd
Product:	[Retired] Red Hat Linux	Reporter:	Per Steinar Iversen <persteinar.iversen>
Component:	pump	Assignee:	Elliot Lee <sopwith>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-06-28 16:14:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Per Steinar Iversen 2001-02-23 16:07:02 UTC

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.

Comment 1 Per Steinar Iversen 2001-02-24 14:39:10 UTC

Sorry - it is pump that misbehaves, actually dhcpcd works fine. Pump though is
broken as described, it can not handle unknown dhcp options.

Comment 2 Elliot Lee 2001-08-26 21:43:10 UTC

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?

Comment 3 Per Steinar Iversen 2001-08-27 06:23:34 UTC

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.