Skip to main content
Talos Linux runs by default a DHCP client on all physical network interfaces to obtain IP addresses and other network settings automatically. Once any explicit link configuration is applied, the default DHCP behavior is disabled, and DHCP must be explicitly enabled on the desired link(s). DHCP allows to configure addresses, routes, DNS, and NTP settings dynamically from a DHCP server. DHCP client can be enabled on physical and logical links (bridges, bonds, VLANs). There are two DHCP versions supported in Talos Linux: DHCPv4 and DHCPv6.

​
DHCPv4 configuration

To enable DHCPv4 on a physical link, create a DHCPv4Config configuration document with the name of the link:
Additional settings can be configured:
  • ignoreHostname: true: ignore the hostname provided by the DHCP server.
  • routeMetric: 512: set the metric for routes provided by DHCP.
  • clientIdentifier: configures the DHCP client identifier, which can have one of the following values:
    • mac: use the MAC address as the client identifier (default).
    • duid: use a DUID (DHCP Unique Identifier) as the client identifier, requires duidRaw field to be set.
    • off: disable the client identifier.

​
DHCPv6 configuration

To enable DHCPv6 on a physical link, create a DHCPv6Config configuration document with the name of the link:
Additional settings are identical to DHCPv4.

​
Observing status

Use talosctl to get the list of all configured operators (which includes DHCP clients):
To see operator configuration broken down by configuration source, add --namespace=network-config flag: