From ArchWiki
Revision as of 02:31, 24 July 2013 by Kynikos (talk | contribs) (Listening on only one interface: use Accuracy template)
Jump to navigation Jump to search

dhcpd is the Internet Systems Consortium DHCP Server. It is useful for instance on a machine acting as a router on a LAN.


Install the dhcp package, available in the official repositories.


Assign an static IPv4 address to the interface you want to use (usually eth0). The first 3 bytes of this address cannot be exactly the same as those of another interface.

# ip link set up dev eth0
# ip addr add dev eth0 # arbitrary address

To have your static ip assigned at boot, you can use netcfg.

The default dhcpd.conf contains many uncommented examples, so relocate it

# mv /etc/dhcpd.conf /etc/dhcpd.conf.example

Edit the configuration file to contain:

# Using the google's dns in the example.
# Change it to if you have a dns server installed
option domain-name-servers;
option subnet-mask;
option routers;
subnet netmask {

Start, and optionally, enable for autostart on boot, the dhcpd4.service daemon.

Read Daemons for more information.

Now, any computer you connect over ethernet will be assigned an IPv4 address (from to in this example).

Tips and Tricks

Listening on only one interface

If your computer is already part of one or several networks, it could be a problem if your computer starts giving ip addresses to machines from the other networks.

In order to force the DHCP server to listen only on one of the network interfaces, you need to specify it in the dhcpd command line.

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: This appears not to work as of ArchLinux 2013-07-01 - see talk page for details. (Discuss in Talk:Dhcpd#)

This is done by editing the configuration file:

# Assuming the device of your lan is eth1
DHCP4_ARGS="-q eth1"

Another step is to tell the routing table on which interface to listen to for the broadcasts:

# ip route add dev eth1

Now, the clients on eth1 will be managed by your DHCP server without having any impact on any client / server on any other ntework interface.


You will see configuration files, etc. related to dhcpcd. That one is the DHCP client executable and has nothing to do with dhcpd.

See also