Dynamic Host Configuration Protocol
dhcrelay utility provides a means for
relaying DHCP and BOOTP requests from a subnet to which no DHCP server is
directly connected to one or more DHCP servers on other subnets.
dhcrelay listens for DHCP requests on a
given interface. When a query is received,
forwards it to the list of DHCP servers specified on the command line. When
a reply is received, it is broadcast or unicast on the network from whence
the original request came.
The name of at least one DHCP server to which DHCP and BOOTP
requests should be relayed, as well as the name of the network interface
dhcrelay should attempt to configure, must be
specified on the command line.
dhcrelay supports relaying of DHCP traffic
to configure IPsec tunnel mode clients when listening on the
enc(4) interface. The DHCP server has to support RFC 3046 to echo
back the relay agent information to allow stateless DHCP reply to IPsec
The options are as follows:
dhcrelaynormally runs in the foreground until it has configured an interface, and then reverts to running in the background. This option forces
dhcrelayto always run as a foreground process.
- The name of the network interface that
dhcrelayshould attempt to configure. At least one IPv4 address has to be configured on this interface.
- Add the relay agent information option. By default, this is only enabled for the enc(4) interface.
R. Droms, Dynamic Host Configuration Protocol, RFC 2131, March 1997.
S. Alexander and R. Droms, DHCP Options and BOOTP Vendor Extensions, RFC 2132, March 1997.
M. Patrick, DHCP Relay Agent Information Option, RFC 3046, January 2001.
B. Patel, B. Aboba, S. Kelly, and V. Gupta, Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode, RFC 3456, January 2003.
dhcrelay was written by
The current implementation was reworked by Henning Brauer <firstname.lastname@example.org>.
Relayed DHCP traffic could actually safely be protected by IPsec
but, like dhcpd(8) and
dhcrelay will bypass IPsec for
all its traffic.