man.bsd.lv manual page server

DESCRIPTION

Information typically contained within a DHCP response includes an IP address for the interface, subnet mask, broadcast address, router (gateway) listing, domain name server listing, and the interface's MTU.

To set up DragonFly as a DHCP client:

1. For each interface that is to be configured via DHCP, add “DHCP” to the ifconfig_⟨interface⟩ variable in /etc/rc.conf. See rc.conf(5) for more information on the format of this file.

   The /etc/network.subr script reads each of these variables at boot-time and runs the DHCP client, e.g., dhclient(8) or dhcpcd(8), for each interface that is to be configured via DHCP.

2. [Optional] To tweak settings, edit /etc/dhclient.conf (if dhcp_client="dhclient") or /etc/dhcpcd.conf (if dhcp_client="dhcpcd"). See dhclient.conf(5) and dhcpcd.conf(5) for details.

To set up DragonFly as a DHCP server:

1. Install dhcpd(8) (available in dports(7)).
2. Edit /usr/local/etc/dhcp/dhcpd.conf. See dhcpd.conf(5) and dhcpd(8) for details.
3. Edit /etc/rc.conf and set dhcpd_flags="". This will cause DragonFly to start the dhcpd(8) daemon at boot-time and listen for DHCP requests on the local network. To start it manually, execute the following command:
   # /usr/local/sbin/dhcpd [netif1 netif2 ...]

The DHCP client and server use the Berkeley Packet Filter (BPF). Ensure the kernel has been compiled with BPF support and at least one /dev/bpf* file exists per broadcast network interface that is attached to the system. This is almost always the case and should only be considered if all other troubleshooting options have failed.

See dhcpd(8) for information on other available options. Note, however, that most of the flags are useful only for debugging purposes.