Sunday, 22 May 2011

Working With DHCP Server In Linux

Normally if you have a cable modem or DSL, you get your home PC's IP address dynamically assigned from your service provider. If you install a home cable/DSL router between your modem and home network, your PC will most likely get its IP address at boot time from the home router instead. You can choose to disable the DHCP server feature on your home router and set up a Linux box as the DHCP server.

Download and Install the DHCP Package
Most RedHat and Fedora Linux software product packages are available in the RPM format, whereas Debian and Ubuntu Linux use DEB format installation files. When searching for these packages, remember that the filename usually starts with the software package name and is followed by a version number, as in dhcp-3.23.58-4.i386.rpm.
Note: With Fedora / Redhat the package to install would be dhcp. With Debian / Ubuntu the package is dhcp3-server.

Starting the DHCP Server
The methodologies vary depending on the variant of Linux you are using as you’ll see next.
Note: Make sure you configure your server before starting!
Fedora / CentOS / RedHat
With these flavors of Linux you can use the chkconfig command to get dhcpd configured to start at boot:
[root@bigboy tmp]# chkconfig dhcpd on
To start, stop, and restart dhcpd after booting use the service command:
[root@bigboy tmp]# service dhcpd start
[root@bigboy tmp]# service dhcpd stop
[root@bigboy tmp]# service dhcpd restart
To determine whether dhcpd is running you can issue either of these two commands. The first will give a status message. The second will return the process ID numbers of the dhcpd daemons.
[root@bigboy tmp]# service dhcpd status
[root@bigboy tmp]# pgrep dhcpd
Note: Remember to run the chkconfig command at least once to ensure dhcpd starts automatically on your next reboot.
Ubuntu / Debian
With these flavors of Linux the commands are different. Try installing the sysv-rc-conf and sysvinit-utils DEB packages as they provide commands that simplify the process. For help on downloading and installing the packages, see Chapter 6, "Installing Linux Software".) You can use the sysv-rc-conf command to get dhcp3-server configured to start at boot:
user@ubuntu:~$ sudo sysv-rc-conf dhcp3-server on
To start, stop, and restart dhcpd after booting the service command is the same:
user@ubuntu:~$ sudo service dhcp3-server start
user@ubuntu:~$ sudo service dhcp3-server stop
user@ubuntu:~$ sudo service dhcp3-server restart
To determine whether dhcpd is running you can issue either of these two commands. The first will give a status message. The second will return the process ID numbers of the dhcpd daemons.  
user@ubuntu:~$ sudo service dhcp3-server status
user@ubuntu:~$ pgrep dhcp
Note: Remember to run the sysv-rc-conf command at least once to ensure mysql starts automatically on your next reboot.
dhcpd.conf File
You can define your server configuration parameters in the dhcpd.conf file which may be located in the /etc the /etc/dhcpd or /etc/dhcp3 directories depending on your version of Linux.
Note: The skeleton dhcp.conf file that is created when you install the package may vary in its completeness. In Ubuntu / Debian, the skeleton dhcpd.conf file is extensive with most of the commands deactivated with a # sign at the beginning. In Fedora / RedHat / CentOS an extensive sample is also created with activated commands. It is found in the following location which you can always use as a guide.
Note: The dhcpd.conf configuration file formats in Debian / Ubuntu and Redhat / Fedora are identical.
Here is a quick explanation of the dhcpd.conf file: Most importantly, there must be a subnet section for each interface on your Linux box.
ddns-update-style interim
ignore client-updates

subnet netmask {

   # The range of IP addresses the server
   # will issue to DHCP enabled PC clients
   # booting up on the network


   # Set the amount of time in seconds that
   # a client may keep the IP address

  default-lease-time 86400;
  max-lease-time 86400;

   # Set the default gateway to be used by
   # the PC clients

   option routers;
   # Don't forward DHCP requests from this
   # NIC interface to any other NIC
   # interfaces

   option ip-forwarding off;

   # Set the broadcast address and subnet mask
   # to be used by the DHCP clients

  option broadcast-address;
  option subnet-mask;
   # Set the NTP server to be used by the
   # DHCP clients

  option ntp-servers;

   # Set the DNS server to be used by the
   # DHCP clients

  option domain-name-servers;

   # If you specify a WINS server for your Windows clients,
   # you need to include the following option in the dhcpd.conf file:

  option netbios-name-servers;

   # You can also assign specific
   # ethernet MAC address as follows (Host's name is "laser-printer":

  host laser-printer {
      hardware ethernet 08:00:2b:4c:59:23;
# List an unused interface here
subnet netmask {
There are many more options statements you can use to configure DHCP. These include telling the DHCP clients where to go for services such as finger and IRC. Check the dhcp-options man page after you do your install:
[root@bigboy tmp]# man dhcp-options
Note: The host statement seen in the sample dhcpd.conf file can be very useful. Some devices such as network printers default to getting their IP addresses using DHCP, but users need to access them by a fixed IP address to print their documents. This statement can be used to always provide specific IP address to DHCP queries from a predefined a NIC MAC address. This can help to reduce systems administration overhead.
DHCP Servers with Multiple NICs
DHCP servers with multiple interfaces pose two configuration challenges. The first is setting up the correct routing and the second is making sure only the required interfaces are listening to serve DHCP. Don’t worry, both will be discussed next.
When a DHCP configured PC boots, it requests its IP address from the DHCP server. It does this by sending a standardized DHCP broadcast request packet to the DHCP server with a source IP address of
If your DHCP server has more than one interface, you have to add a route for this address so that it knows the interface on which to send the reply; if not, it sends it to the default gateway. (In both of the next two examples, we assume that DHCP requests will be coming in on interface eth0). 

Note: You can't run your DHCP sever on multiple interfaces because you can only have one route to network If you try to do it, you'll discover that DHCP serving working on only one interface.
Temporary Solution
You can temporarily add a route to using the route add command as seen below.
[root@bigboy tmp]# route add -host dev eth0
If you want this routing state to be maintained after a reboot, then use the permanent solution that's discussed next.
Permanent Solution
Create a permanent route to This will vary according to your version of Linux
Fedora / RedHat / CentOS: Add the route to your /etc/sysconfig/network-scripts/route-eth0 file if the route needs to be added to your eth0 interface.
# File /etc/sysconfig/network-scripts/route-eth0
# dev eth0
Ubuntu / Debian: Add the route to your /etc/network/interfaces file. In this case the route is added to the eth0 interface.
# File: /etc/network/interfaces

iface eth0 inet static

       up route add -host eth0

Once you have defined the interface for your DHCP routing you should also ensure that your DHCP server only listens on that interface and no others. This methodology to do this varies depending on your versiĆ³n of Linux.
Fedora / RedHat / CentOS: The /etc/sysconfig/dhcpd file must be edited and the DHCPDARGS variable edited to include the preferred interface. In this example interface eth0 is preferred.
# File: /etc/sysconfig/dhcpd
Debian / Ubuntu: The /etc/default/dhcp3-server file must be edited and the INTERFACES variable edited to include the preferred interface. In this example interface eth0 is preferred.
# File: /etc/default/dhcp3-server
You will be able to verify success in one of two ways. First the netstat command using the –au options will give the list of interfaces listening on the bootp (DHCP) UDP port.
[root@bigboy-f ~]# netstat -au  | grep bootp
udp        0     0    *:*
[root@bigboy-f ~]#
Secondly, your /var/log/messages file will also reveal the defined interfaces used when the DHCPd daemon was restarted.
Jan  8 17:22:44 bigboy dhcpd: Listening on LPF/eth0/00:e0:18:5c:d8:41/
Jan  8 17:22:44 bigboy dhcpd: Sending on   LPF/eth0/00:e0:18:5c:d8:41/
Success! You can go back to lunch!

Using a Single DHCP Server to Serve Multiple Networks
As stated before, DHCP clients send their requests for IP addresses to a broadcast address which is limited to the local LAN. This would imply that a DHCP server is required on each subnet. Not so. It is possible to configure routers to forward DHCP requests to a DHCP server many hops away. This is done by inserting the IP address of the router's interface on the DHCP client's network into the forwarded packet. To the DHCP server, the non-blank router IP address field takes precedence over the broadcast address and it uses this value to provide a DHCP address that is meaningful to the client. The DHCP server replies with a broadcast packet, and the router, which has kept track of the initial forwarded request, forwards it back towards the client. You can configure this feature on Cisco devices by using the ip helper-address command on all the interfaces on which DHCP clients reside. Here is a configuration sample that points to a DHCP server with the IP address
interface FastEthernet 2/1
  ip address
  ip helper-address
Simple DHCP Troubleshooting
The most common problems with DHCP usually aren't related to the server; after the server is configured correctly there is no need to change any settings and it therefore runs reliably. The problems usually occur at the DHCP client's end for a variety of reasons. The following sections present simple troubleshooting steps that you can go through to ensure that DHCP is working correctly on your network.

DHCP Clients Obtaining Addresses
Whenever Microsoft DHCP clients are unable to contact their DHCP server they default to selecting their own IP address from the network until the DHCP server becomes available again. This is frequently referred to as Automatic Private IP Addressing (APIPA). Here are some steps you can go through to resolve the problem:
  • Ensure that your DHCP server is configured correctly and use the pgrep command discussed earlier to make sure the DHCP process is running. Pay special attention to your route, especially if your DHCP server has multiple interfaces.
  • Give your DHCP client a static IP address from the same range that the DHCP server is supposed to provide. See whether you can ping the DHCP server. If you cannot, double-check your cabling and your NIC cards.
  • DHCP uses the BOOTP protocol for its communication between the client and server. Make sure there are no firewalls blocking this traffic. DHCP servers expect requests on UDP port 67 and the DHCP clients expect responses on UDP port 68. Use tcpdump on the server's NIC to verify the correct traffic flows.
Other DHCP Failures
If the DHCP server fails to start then use your regular troubleshooting techniques to help rectify your problems. Most problems with an initial setup are often due to:
  • Incorrect settings in the /etc/dhcpd.conf file such as not defining the networks for which the DHCP server is responsible;
  • Firewall rules that block the DHCP bootp protocol on UDP ports 67 and 68;
  • Routers failing to forward the bootp packets to the DHCP server when the clients reside on a separate network.
Always check your /var/logs/messages file for dhcpd errors and remember that mandatory keywords in your configuration file may change when you upgrade your operating system. Always read the release notes to be sure.

1 comment:

  1. Hi, do you happen to have the dhcp-3.23.58-4.i386.rpm file? Is it possible that you can send it to me? My email is I would really appreciate it. Thank you in advance.