networkd.conf(5)

1NETWORKD.CONF(5)                 networkd.conf                NETWORKD.CONF(5)
2
3
4

NAME

6       networkd.conf, networkd.conf.d - Global Network configuration files
7

SYNOPSIS

9       /etc/systemd/networkd.conf
10
11       /etc/systemd/networkd.conf.d/*.conf
12
13       /usr/lib/systemd/networkd.conf.d/*.conf
14

DESCRIPTION

16       These configuration files control global network parameters. Currently
17       the DHCP Unique Identifier (DUID).
18

CONFIGURATION DIRECTORIES AND PRECEDENCE

20       The default configuration is defined during compilation, so a
21       configuration file is only needed when it is necessary to deviate from
22       those defaults. By default, the configuration file in /etc/systemd/
23       contains commented out entries showing the defaults as a guide to the
24       administrator. This file can be edited to create local overrides.
25
26       When packages need to customize the configuration, they can install
27       configuration snippets in /usr/lib/systemd/*.conf.d/. Files in /etc/
28       are reserved for the local administrator, who may use this logic to
29       override the configuration files installed by vendor packages. The main
30       configuration file is read before any of the configuration directories,
31       and has the lowest precedence; entries in a file in any configuration
32       directory override entries in the single configuration file. Files in
33       the *.conf.d/ configuration subdirectories are sorted by their filename
34       in lexicographic order, regardless of which of the subdirectories they
35       reside in. When multiple files specify the same option, for options
36       which accept just a single value, the entry in the file with the
37       lexicographically latest name takes precedence. For options which
38       accept a list of values, entries are collected as they occur in files
39       sorted lexicographically. It is recommended to prefix all filenames in
40       those subdirectories with a two-digit number and a dash, to simplify
41       the ordering of the files.
42
43       To disable a configuration file supplied by the vendor, the recommended
44       way is to place a symlink to /dev/null in the configuration directory
45       in /etc/, with the same filename as the vendor configuration file.
46

[DHCP] SECTION OPTIONS

48       This section configures the DHCP Unique Identifier (DUID) value used by
49       DHCP protocol. DHCPv6 client protocol sends the DHCP Unique Identifier
50       and the interface Identity Association Identifier (IAID) to a DHCP
51       server when acquiring a dynamic IPv6 address. DHCPv4 client protocol
52       sends IAID and DUID to the DHCP server when acquiring a dynamic IPv4
53       address if ClientIdentifier=duid. IAID and DUID allows a DHCP server to
54       uniquely identify the machine and the interface requesting a DHCP IP.
55       To configure IAID and ClientIdentifier, see systemd.network(5).
56
57       The following options are understood:
58
59       DUIDType=
60           Specifies how the DUID should be generated. See RFC 3315[1] for a
61           description of all the options.
62
63           The following values are understood:
64
65           vendor
66               If "DUIDType=vendor", then the DUID value will be generated
67               using "43793" as the vendor identifier (systemd) and hashed
68               contents of machine-id(5). This is the default if DUIDType= is
69               not specified.
70
71           uuid
72               If "DUIDType=uuid", and DUIDRawData= is not set, then the
73               product UUID is used as a DUID value. If a system does not have
74               valid product UUID, then an application-specific machine-id(5)
75               is used as a DUID value. About the application-specific machine
76               ID, see sd_id128_get_machine_app_specific(3).
77
78           link-layer-time[:TIME], link-layer
79               If "link-layer-time" or "link-layer" is specified, then the MAC
80               address of the interface is used as a DUID value. The value
81               "link-layer-time" can take additional time value after a colon,
82               e.g.  "link-layer-time:2018-01-23 12:34:56 UTC". The default
83               time value is "2000-01-01 00:00:00 UTC".
84
85           In all cases, DUIDRawData= can be used to override the actual DUID
86           value that is used.
87
88       DUIDRawData=
89           Specifies the DHCP DUID value as a single newline-terminated,
90           hexadecimal string, with each byte separated by ":". The DUID that
91           is sent is composed of the DUID type specified by DUIDType= and the
92           value configured here.
93
94           The DUID value specified here overrides the DUID that systemd-
95           networkd.service(8) generates from the machine ID. To configure
96           DUID per-network, see systemd.network(5). The configured DHCP DUID
97           should conform to the specification in RFC 3315[2], RFC 6355[3]. To
98           configure IAID, see systemd.network(5).
99
100           Example 1. A DUIDType=vendor with a custom value
101
102               DUIDType=vendor
103               DUIDRawData=00:00:ab:11:f9:2a:c2:77:29:f9:5c:00
104
105           This specifies a 14 byte DUID, with the type DUID-EN ("00:02"),
106           enterprise number 43793 ("00:00:ab:11"), and identifier value
107           "f9:2a:c2:77:29:f9:5c:00".
108

NOTES

114        1. RFC 3315
115           https://tools.ietf.org/html/rfc3315#section-9
116
117        2. RFC 3315
118           http://tools.ietf.org/html/rfc3315#section-9
119
120        3. RFC 6355
121           http://tools.ietf.org/html/rfc6355
122
123
124
125systemd 241                                                   NETWORKD.CONF(5)

NAME

SYNOPSIS

DESCRIPTION

CONFIGURATION DIRECTORIES AND PRECEDENCE

[DHCP] SECTION OPTIONS

SEE ALSO

NOTES