dhcpd - A component for configuring the dhcpd service
This component will build an /etc/dhcpd.conf file for the dhcp daemon based on information published by prospective DHCP clients to the spanning map specified by the cluster resource.
Each client must define a dhclient.mac resource; it should define a dhclient.hostname resource if its correct fully qualified domain name is not implied by its LCFG source profile name and the default DNS domain; and it may also define other dhcpd settings via dhclient resources, which then take precedence over the corresponding settings in force either globally or by subnet.
DHCP service for a client's Baseboard Management Controller (BMC) is also supported. Should this be required, the client must define both a dhclient.bmcmac resource and a dhclient.bmchostname resource.
As well as providing for fixed address allocation, this component allows a range of dynamic addresses to be defined per subnet.
The full pathname of the dhcpd binary in use on the DHCP server. The default is /usr/sbin/dhcpd.
The full pathname of the dhcpd daemon's configuration file. The default is /etc/dhcpd.conf.
The full pathname of the `/etc/init.d' script used to stop and start the dhcpd daemon. The default is /etc/rc.d/init.d/dhcpd.
The full pathname of the file containing the PID of the running dhcpd daemon. The default is /var/run/dhcpd.pid.
The full pathname of the directory in which the dhcpd daemon's leases database file is stored. The default is /var/lib/dhcpd.
A list of the interfaces on the server for which DHCP service is to be configured.
An email address for admin emails from the component.
The name of the spanning map to which this component should subscribe in order to receive configuration information published by each prospective client. The default is dhcp/all.
A tag list of hosts produced by the spanning map subscription. Each host is a prospective DHCP client. The spanning map then makes the following resources available per client:
The hostname to set for the client.
The MAC address of the client, in the format six groups of two hexadecimal digits, separated by either colons or hyphens (eg 01:23:45:67:89:AB).
The name of the grub menu file to be downloaded by the client.
The name of bootable file to be tftp'ed by the client.
The fully qualified hostname to set for the client's BMC, should this also require DHCP configuration.
The MAC address of the client's BMC, should this also require DHCP configuration, in the format six groups of two hexadecimal digits, separated by either colons or hyphens (eg 01:23:45:67:89:AB).
If defined to any non-null value, configures the DHCP server as authoritative.
The default dns domain.
The default nisdomain.
A space separated list of mailservers.
A space separated list of ntp servers.
The NetBIOS node type option allows NetBIOS over TCP/IP clients which are configurable to be configured as described in RFC 1001/1002.
The NetBIOS name server (NBNS) option specifies a list of RFC 1001/1002 NBNS name servers listed in order of preference. NetBIOS Name Service is currently more commonly referred to as WINS. WINS servers can be specified using the netbios-name-servers option.
Set to on (the default) for router discovery.
Set to yes to allow the dhcpd server to answer bootp requests. The default is no.
The convention used to pass dynamic dns updates to the dns server. The default is `none'.
The multicast tftpd server address for PXE booting.
A tag list of user defined options. (For further information on such options, see the `Defining New Options' section of dhcpd-options(5).)
The name of the option.
The bootp/dhcp option code the option refers to.
The type (text, ipaddr etc) the option has.
The value of this option.
A list of user defined option spaces.
A tag list of the subnets for which DHCP service is to be provided.
There is a corresponding list of resources which can be set on a by subnet basis, some of which override global settings of the same name listed above. Inspection of this component's schema file, along with the dhcpd.conf(5), man page is recommended.
The component is currently fairly messy, and needs to be expanded to cope with additional options.
Currently unsupported features (note that this list is unlikely to be either definitive or accurate):
shared-network
user defined options
overloading of all options at subnet level
overloading of all options at host level
the group declaration
dhcpd.conf(5), dhcpd-options(5), dhcpd(8)
Fedora5, Fedora6, Scientific5
Iain Rae <iainr@inf.ed.ac.uk>, Ian Durkacz <idurkacz@inf.ed.ac.uk>