1NETWORKD.CONF(5) networkd.conf NETWORKD.CONF(5)
2
6 networkd.conf, networkd.conf.d - Global Network configuration files
7
9 /etc/systemd/networkd.conf
10 /etc/systemd/networkd.conf.d/*.conf
12 /usr/lib/systemd/networkd.conf.d/*.conf
14
16 These configuration files control global network parameters. Currently
17 the DHCP Unique Identifier (DUID).
18
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 When packages need to customize the configuration, they can install
27 configuration snippets in /usr/lib/systemd/*.conf.d/ or
28 /usr/local/lib/systemd/*.conf.d/. The main configuration file is read
29 before any of the configuration directories, and has the lowest
30 precedence; entries in a file in any configuration directory override
31 entries in the single configuration file. Files in the *.conf.d/
32 configuration subdirectories are sorted by their filename in
33 lexicographic order, regardless of in which of the subdirectories they
34 reside. When multiple files specify the same option, for options which
35 accept just a single value, the entry in the file with the
36 lexicographically latest name takes precedence. For options which
37 accept a list of values, entries are collected as they occur in files
38 sorted lexicographically.
39 Files in /etc/ are reserved for the local administrator, who may use
41 this logic to override the configuration files installed by vendor
42 packages. It is recommended to prefix all filenames in those
43 subdirectories with a two-digit number and a dash, to simplify the
44 ordering of the files.
45 To disable a configuration file supplied by the vendor, the recommended
47 way is to place a symlink to /dev/null in the configuration directory
48 in /etc/, with the same filename as the vendor configuration file.
49
51 The following options are available in the [Network] section:
52 SpeedMeter=
54 Takes a boolean. If set to yes, then systemd-networkd measures the
55 traffic of each interface, and networkctl status INTERFACE shows
56 the measured speed. Defaults to no.
57 SpeedMeterIntervalSec=
59 Specifies the time interval to calculate the traffic speed of each
60 interface. If SpeedMeter=no, the value is ignored. Defaults to
61 10sec.
62 ManageForeignRoutes=
64 A boolean. When true, systemd-networkd will store any routes
65 configured by other tools in its memory. When false,
66 systemd-networkd will not manage the foreign routes, thus they are
67 kept even if KeepConfiguration= is false. Defaults to yes.
68
70 This section configures the DHCP Unique Identifier (DUID) value used by
71 DHCP protocol. DHCPv6 client protocol sends the DHCP Unique Identifier
72 and the interface Identity Association Identifier (IAID) to a DHCP
73 server when acquiring a dynamic IPv6 address. DHCPv4 client protocol
74 sends IAID and DUID to the DHCP server when acquiring a dynamic IPv4
75 address if ClientIdentifier=duid. IAID and DUID allows a DHCP server to
76 uniquely identify the machine and the interface requesting a DHCP IP.
77 To configure IAID and ClientIdentifier, see systemd.network(5).
78 The following options are understood:
80 DUIDType=
82 Specifies how the DUID should be generated. See RFC 3315[1] for a
83 description of all the options.
84 The following values are understood:
86 vendor
88 If "DUIDType=vendor", then the DUID value will be generated
89 using "43793" as the vendor identifier (systemd) and hashed
90 contents of machine-id(5). This is the default if DUIDType= is
91 not specified.
92 uuid
94 If "DUIDType=uuid", and DUIDRawData= is not set, then the
95 product UUID is used as a DUID value. If a system does not have
96 valid product UUID, then an application-specific machine-id(5)
97 is used as a DUID value. About the application-specific machine
98 ID, see sd_id128_get_machine_app_specific(3).
99 link-layer-time[:TIME], link-layer
101 If "link-layer-time" or "link-layer" is specified, then the MAC
102 address of the interface is used as a DUID value. The value
103 "link-layer-time" can take additional time value after a colon,
104 e.g. "link-layer-time:2018-01-23 12:34:56 UTC". The default
105 time value is "2000-01-01 00:00:00 UTC".
106 In all cases, DUIDRawData= can be used to override the actual DUID
108 value that is used.
109 DUIDRawData=
111 Specifies the DHCP DUID value as a single newline-terminated,
112 hexadecimal string, with each byte separated by ":". The DUID that
113 is sent is composed of the DUID type specified by DUIDType= and the
114 value configured here.
115 The DUID value specified here overrides the DUID that systemd-
117 networkd.service(8) generates from the machine ID. To configure
118 DUID per-network, see systemd.network(5). The configured DHCP DUID
119 should conform to the specification in RFC 3315[2], RFC 6355[3]. To
120 configure IAID, see systemd.network(5).
121 Example 1. A DUIDType=vendor with a custom value
123 DUIDType=vendor
125 DUIDRawData=00:00:ab:11:f9:2a:c2:77:29:f9:5c:00
126 This specifies a 14 byte DUID, with the type DUID-EN ("00:02"),
128 enterprise number 43793 ("00:00:ab:11"), and identifier value
129 "f9:2a:c2:77:29:f9:5c:00".
130
132 systemd(1), systemd.network(5), systemd-networkd.service(8), machine-
133 id(5), sd_id128_get_machine_app_specific(3)
134
136 1. RFC 3315
137 https://tools.ietf.org/html/rfc3315#section-9
138 2. RFC 3315
140 http://tools.ietf.org/html/rfc3315#section-9
141 3. RFC 6355
143 http://tools.ietf.org/html/rfc6355
144systemd 246 NETWORKD.CONF(5)