Go to file
2017-04-13 16:16:58 +01:00
compat Update copyrights and headers to better credit the sources. 2017-03-30 21:53:45 +01:00
hooks Fix make proginstall target. 2017-03-31 10:48:42 +01:00
src Reset exitnow on entry in-case we are re-started after an exit. 2017-04-13 14:01:50 +01:00
tests Fix compile on Solaris. 2017-04-13 16:16:58 +01:00
.arcconfig Add an .arcconfig file to hook arcanist with phabricator. 2017-03-24 12:47:16 +00:00
.gitignore Ignore distribution and Coverity files. 2017-03-21 14:12:55 +00:00
BUILDING.md Write syslog entries in logfile: 2017-04-11 18:04:03 +01:00
config-null.mk Compile embedded in without a config 2014-04-23 19:09:03 +00:00
configure With the logger removed, we no longer need to test for printf %m support. 2017-04-02 09:53:17 +01:00
iconfig.mk Load config.{h,mk} when building tests. Fixes [1c11c59282]. 2014-05-30 21:47:14 +00:00
LICENSE Add LICENSE. 2017-03-24 16:23:42 +00:00
Makefile Move test into tests. 2017-04-13 14:50:58 +01:00
Makefile.inc Fix man page paths. 2017-03-21 15:28:03 +00:00
README.md Disable NTP in the default config. 2017-03-15 22:16:18 +00:00

dhcpcd

dhcpcd is a DHCP and a DHCPv6 client. It's also an IPv4LL (aka ZeroConf) client. In layman's terms, dhcpcd runs on your machine and silently configures your computer to work on the attached networks without trouble and mostly without configuration.

If you're a desktop user then you may also be interested in Network Configurator (dhcpcd-ui) which sits in the notification area and monitors the state of the network via dhcpcd. It also has a nice configuration dialog and the ability to enter a pass phrase for wireless networks.

dhcpcd may not be the only daemon running that wants to configure DNS on the host, so it uses openresolv to ensure they can co-exist.

See BUILDING.md for how to build dhcpcd.

If you wish to file a support ticket or help out with development, please visit the Development Area or join the mailing list below.

Configuration

You should read the dhcpcd.conf man page and put your options into /etc/dhcpcd.conf. The default configuration file should work for most people just fine. Here it is, in case you lose it.

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
duid

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Respect the network MTU.
option interface_mtu

# Most distributions have NTP support.
#option ntp_servers

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private

The dhcpcd man page has a lot of the same options and more, which only apply to calling dhcpcd from the command line.

Compatibility

dhcpcd-5 is only fully command line compatible with dhcpcd-4 For compatibility with older versions, use dhcpcd-4

Upgrading

dhcpcd-7 defaults the database directory to /var/db/dhcpcd instead of /var/db and now stores dhcpcd.duid and dhcpcd.secret in there instead of in /etc. The Makefile _confinstall target will attempt to move the files correctly from the old locations to the new locations. Of course this won't work if dhcpcd-7 is packaged up, so packagers will need to install similar logic into their dhcpcd package.

ChangeLog

We no longer supply a ChangeLog. However, you're more than welcome to read the commit log and archived release annoucements.