Red Hat Bugzilla – Bug 16431
RFE: dhcpd initscript does not allow one to specify the interface to be served
Last modified: 2008-05-01 11:37:57 EDT
The current initscript for dhcpd does not allow one to specify the
interface or interfaces over which the addresses are to be served. When
used in a gateway configuration with two interfaces, only one of which is
on the internal network, one has to edit the initscript to specify that
address are only served on eth1 for instance.
Second, one must touch /var/lock/subsys/dhcpd.leases, before dhcpd can
start. Shouldn't this be done at install time?
Per discussion over the weekend on the Beta-tester's list, add a file:
and source it in the dhcp initscript, to allow, eg,
OPTIONS=" eth1 "
which is passed to the start) option thus:
daemon /usr/sbin/dhcpd $OPTIONS
Also requires documentation addon in the print docs ...
In the instant example, this allows limiting the DHCP process to listen for
assignment requests only on the 'interior' eth1 interface. Useful (and indeed
the patch I use) with a cable-modem environment
... avoids tampering with the initscript itself.
Somehow this apparently got missed. Seawolf still doesn't have (or the init
script handle) an /etc/sysconfig/dhcp file. Virtually every other service that
takes command line options has this.
Hello /// anyone there? This is still in 'New' status 9 months after initial
submissina, and although re-commented 3 months before Seawolf gold, still
Apologies for the unresponsiveness of the previous dhcpd packager...
This is fixed in my dhcp package by a /etc/sysconfig/dhcpd file.