Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 8281

Summary:	Need to specify dhcpd startup options
Product:	[Retired] Red Hat Linux	Reporter:	Jason Tibbitts <j>
Component:	dhcp	Assignee:	Elliot Lee <sopwith>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.1
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-07-16 13:40:25 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 Jason Tibbitts 2000-01-07 21:57:26 UTC

I need to restrict dhcpd to run on a specific interface, and this can only
be done on its initial command line.  It is trivial to do this by modifying
/etc/rd.c/init.d/dhcpd, but this file is not tagged in the RPM as a
configuration file (and indeed shouldn't be) so upgrades may not preserve
it.

It would be great if I could set something like DHCPD_STARTUP_OPTIONS in
/etc/sysconfig/network or /etc/sysconfig/dhcpd instead of modifying an
init.d file manually.

Thanks!

Comment 1 Tobias Ringstrom 2001-04-10 16:48:53 UTC

I think the above is an excellent proposal, but I fail to understand how a bug 
can be NEW for over a year.  Would a patch help?

Comment 2 Elliot Lee 2001-07-16 23:38:22 UTC

Although pump has been the DHCP client impl of choice for a few versions,
rawhide currently uses dhcpcd in a way that would seem to solve this problem
transparently (because dhcpcd is run per-interface, etc.)

Comment 3 Jason Tibbitts 2001-07-16 23:53:30 UTC

The issue was with the DHCP server, not the client.

A machine with two interfaces might serve DHCP to one of them but doing so for
the other could cause serious chaos.  It's no big deal to edit /etc/init.d/dhcpd
to fix this, but it would be nice if there was a supported way to do it without
editing.  Originally I though that an upgrade would wipe the manual changes out,
but that turns out not to be the case, so it's even less of an issue than I
thought it was so long ago.  Editing the startup file has become an automatic
part of setting up any new server for me.

Comment 4 Elliot Lee 2001-07-17 00:03:46 UTC

My mistake on the package.

I have a system that is supposed to serve DHCP on only one of its two
interfaces, and the solution I use is to have an entry corresponding to the
"don't serve DHCP" interface that looks like so:

subnet 207.175.42.0 netmask 255.255.254.0 {
  not authoritative;
}

I seem to vaguely recall having problems getting your approach to work when I
was setting this up, which is why I used this approach.

Anyways, I've added a /etc/sysconfig/dhcpd to dhcp-2.0pl5-6, which should show
up in rawhide soon and give you the option of using your approach.