Chapter - 13 Dynamic Host Configuration Protocol (DHCP)

Chapter – 13
Dynamic Host Configuration

Protocol (DHCP)
Objectives:
At the end of this module, you would

have gained fair knowledge on:
•Use of DHCP
•Configuring DHCP
Dynamic Host Configuration
Protocol (DHCP) is network protocol
for automatically assigning TCP/IP
information to client machines. Each
DHCP client connects to the centrally
located DHCP server that returns the
client's network configuration including
IP address, gateway, and DNS
servers.
Why Use DHCP?
DHCP is useful for fast delivery of client network
configuration. When configuring the client system, the
administrator can choose DHCP and not have to enter an IP
address, netmask, gateway, or DNS servers.
The client retrieves this information from the

DHCP server. DHCP is also useful if an administrator wants to
change the IP address of a large number of systems. Instead of
reconfiguring all the systems, he can just edit one DHCP
configuration file on the server for the new set of IP address.
If the DNS servers for an organization

changes, the changes are made on the DHCP server, not on all
the DHCP clients
Configuring a DHCP Server
You can configure a DHCP server using the
configuration file /etc/dhcpd.conf. DHCP also uses the
file /var/lib/dhcp/dhcpd.leases to store the client lease
database.
Configuration File
The first step in configuring a DHCP server is
to create the configuration file that stores the network
information for the clients. Global options can be
declared for all clients, or options can be declared for
each client system.
The configuration file can contain any extra
tabs or blank lines for easier formatting. The keywords
are case-insensitive, and lines beginning with a hash
mark (#) are considered comments.
If you change the configuration file, the changes will
not take effect until you restart the DHCP daemon with the command
service dhcpd restart.
You can declare a subnet. You must include a subnet declaration for
every subnet in your network. If you do not, the DHCP server will fail to
start.
In this example, there are global options for every DHCP client
in the subnet and a range declared. Clients are assigned an IP
address within the range.
subnet 192.168.1.0 netmask 255.255.255.0 {

option routers 192.168.1.254;
option subnet-mask 255.255.255.0;
option domain-name "example.com";
option domain-name-servers 192.168.1.1;
option time-offset -5; # Eastern Standard Time
range 192.168.1.10 192.168.1.100;
}
To configure a DHCP server that
leases dynamic IP address to system within a subnet,
modify with your values. It declares a default lease time,
maximum lease time, and network configuration values for
the clients. This example assigns IP address in the range
192.168.1.10 and 192.168.1.100 to client systems.
default-lease-time 600;
max-lease-time 7200;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.254;
option domain-name-servers 192.168.1.1,
192.168.1.2;
option domain-name "example.com";
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.10 192.168.1.100;
}
To assign an IP address to a
client based on the MAC address of the network interface
card, use the hardware ethernet parameter within a host
declaration. The host apex declaration specifies that the
network interface card with the MAC address
00:A0:78:8E:9E:AA should always been leased the IP
address 192.168.1.4.
Notice that you can also use the optional

parameter host-name to assign a host name to the client.
host apex {
option host-name apex.example.com";
hardware ethernet 00:A0:78:8E:9E:AA;
fixed-address 192.168.1.4;
}
Lease Database
On the DHCP server, the file
/var/lib/dhcp/dhcpd.leases stores the DHCP client
lease database. This file should not be modified by
hand. DHCP lease information for each recently
assigned IP address is automatically stored in the
lease database.
The information includes the length of the
lease, to whom the IP address has been assigned, the
start and end dates for the lease, and the MAC
address of the network interface card that was used to
retrieve the lease.
The first time you start the DHCP
service, it will fail unless the lease database
exists. Use the command
touch /var/lib/dhcpd.leases to create the file
before starting the server for the first time. Once
the file exists and the server has been started, do
not try to create a new lease database file.
The lease database is recreated
from time to time so that it is not too large. First,
all known leases are saved in a temporary lease
database. The dhcpd.leases file is renamed
dhcpd.leases~, and the temporary lease
database is written to dhcpd.leases.
The DHCP daemon could be killed or
the system could crash after the lease
database has been renamed to the backup
file but before the new file has been written.
If this happens, there is no
dhcpd.leases file that is required to start the
service. Do not create a new lease file if this
occurs. If you do, all the old leases will be
lost and cause many problems.
The correct solution is to rename
the dhcpd.leases~ backup file to
dhcpd.leases and then start the daemon.
Starting and Stopping the Server
To start the DHCP service, use the command
/sbin/service dhcpd start.
To stop the DHCP server, use the command
/sbin/service dhcpd stop.
DHCP Relay Agent

The DHCP Relay Agent (dhcprelay) allows you to relay DHCP and
BOOTP requests from a subnet with no DHCP server on it to one
or more DHCP servers on other subnets. When DHCP client
requests information, the DHCP Relay Agent forwards the request
to the list of DHCP servers specified when the DHCP Relay Agent
is started. When a DHCP server returns a reply, the reply is
broadcast or unicast on the network that sent the original request.
To start the DHCP Relay Agent, use the dhcrelay command.
Configuring a DHCP Client
The first step for configuring a DHCP client is to
make sure the kernel recognizes the network interface card.
Most cards are recognized during the installation process, and
the system is configured to use the correct kernel module for
the card. If you install a card after installation, Kudzu should
recognize it and prompt you to configure the corresponding
kernel module for it.
To configure a DHCP client manually, you need
to modify the /etc/sysconfig/network file to enable networking
and the configuration file for each network device in the
/etc/sysconfig/network-scripts directory. In this directory,
each device should have a configuration file named ifcfg-eth0
where eth0 is the network device name.
The /etc/sysconfig/network file should
contain the following line
NETWORKING=yes
The /etc/sysconfig/network-scripts/ifcfg-eth0 file

should contain the following lines:
DEVICE=eth0
BOOTPROTO=dhcpO
NBOOT=yes
You need a configuration file for each device that you

want to configure to use DHCP.

Chapter - 13 Dynamic Host Configuration Protocol (DHCP)

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Chapter - 13 Dynamic Host Configuration Protocol (DHCP)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter - 13 Dynamic Host Configuration Protocol (DHCP)

Uploaded by

Copyright:

Available Formats

Chapter – 13

Dynamic Host Configuration

At the end of this module, you would

The client retrieves this information from the

If the DNS servers for an organization

subnet 192.168.1.0 netmask 255.255.255.0 {

Notice that you can also use the optional

DHCP Relay Agent

The /etc/sysconfig/network-scripts/ifcfg-eth0 file

You need a configuration file for each device that you

You might also like