chiark / gitweb /
journald: add syslog fields for audit messages
[elogind.git] / man / systemd.network.xml
1 <?xml version='1.0'?> <!--*-nxml-*-->
2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3   "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
4
5 <!--
6   This file is part of systemd.
7
8   Copyright 2013 Tom Gundersen
9
10   systemd is free software; you can redistribute it and/or modify it
11   under the terms of the GNU Lesser General Public License as published by
12   the Free Software Foundation; either version 2.1 of the License, or
13   (at your option) any later version.
14
15   systemd is distributed in the hope that it will be useful, but
16   WITHOUT ANY WARRANTY; without even the implied warranty of
17   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
18   Lesser General Public License for more details.
19
20   You should have received a copy of the GNU Lesser General Public License
21   along with systemd; If not, see <http://www.gnu.org/licenses/>.
22 -->
23
24 <refentry id="systemd.network" conditional='ENABLE_NETWORKD'>
25
26   <refentryinfo>
27     <title>systemd.network</title>
28     <productname>systemd</productname>
29
30     <authorgroup>
31       <author>
32         <contrib>Developer</contrib>
33         <firstname>Tom</firstname>
34         <surname>Gundersen</surname>
35         <email>teg@jklm.no</email>
36       </author>
37     </authorgroup>
38   </refentryinfo>
39
40   <refmeta>
41     <refentrytitle>systemd.network</refentrytitle>
42     <manvolnum>5</manvolnum>
43   </refmeta>
44
45   <refnamediv>
46     <refname>systemd.network</refname>
47     <refpurpose>Network configuration</refpurpose>
48   </refnamediv>
49
50   <refsynopsisdiv>
51     <para><filename><replaceable>network</replaceable>.network</filename></para>
52   </refsynopsisdiv>
53
54   <refsect1>
55     <title>Description</title>
56
57     <para>Network setup is performed by
58     <citerefentry><refentrytitle>systemd-networkd</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
59     </para>
60
61     <para>Network files must have the extension
62     <filename>.network</filename>; other extensions are ignored.
63     Networks are applied to links whenever the links appear.</para>
64
65     <para>The <filename>.network</filename> files are read from the
66     files located in the system network directory
67     <filename>/usr/lib/systemd/network</filename>, the volatile
68     runtime network directory
69     <filename>/run/systemd/network</filename> and the local
70     administration network directory
71     <filename>/etc/systemd/network</filename>. All configuration files
72     are collectively sorted and processed in lexical order, regardless
73     of the directories in which they live. However, files with
74     identical filenames replace each other. Files in
75     <filename>/etc</filename> have the highest priority, files in
76     <filename>/run</filename> take precedence over files with the same
77     name in <filename>/usr/lib</filename>. This can be used to
78     override a system-supplied configuration file with a local file if
79     needed; a symlink in <filename>/etc</filename> with the same name
80     as a configuration file in <filename>/usr/lib</filename>, pointing
81     to <filename>/dev/null</filename>, disables the configuration file
82     entirely.</para>
83
84   </refsect1>
85
86   <refsect1>
87     <title>[Match] Section Options</title>
88
89       <para>The network file contains a <literal>[Match]</literal>
90       section, which determines if a given network file may be applied
91       to a given device; and a <literal>[Network]</literal> section
92       specifying how the device should be configured. The first (in
93       lexical order) of the network files that matches a given device
94       is applied.</para>
95
96       <para>A network file is said to match a device if each of the
97       entries in the <literal>[Match]</literal> section matches, or if
98       the section is empty. The following keys are accepted:</para>
99
100       <variablelist class='network-directives'>
101         <varlistentry>
102           <term><varname>MACAddress=</varname></term>
103           <listitem>
104             <para>The hardware address.</para>
105           </listitem>
106         </varlistentry>
107         <varlistentry>
108           <term><varname>Path=</varname></term>
109           <listitem>
110             <para>A whitespace-separated list of shell-style globs
111             matching the persistent path, as exposed by the udev
112             property <literal>ID_PATH</literal>.</para>
113           </listitem>
114         </varlistentry>
115         <varlistentry>
116           <term><varname>Driver=</varname></term>
117           <listitem>
118             <para>A whitespace-separated list of shell-style globs
119             matching the driver currently bound to the device, as
120             exposed by the udev property <literal>DRIVER</literal>
121             of its parent device, or if that is not set the driver
122             as exposed by <literal>ethtool -i</literal> of the
123             device itself.</para>
124           </listitem>
125         </varlistentry>
126         <varlistentry>
127           <term><varname>Type=</varname></term>
128           <listitem>
129             <para>A whitespace-separated list of shell-style globs
130             matching the device type, as exposed by the udev property
131             <literal>DEVTYPE</literal>.</para>
132           </listitem>
133         </varlistentry>
134         <varlistentry>
135           <term><varname>Name=</varname></term>
136           <listitem>
137             <para>A whitespace-separated list of shell-style globs
138             matching the device name, as exposed by the udev property
139             <literal>INTERFACE</literal>.</para>
140           </listitem>
141         </varlistentry>
142         <varlistentry>
143           <term><varname>Host=</varname></term>
144           <listitem>
145             <para>Matches against the hostname or machine ID of the
146             host. See <literal>ConditionHost=</literal> in
147             <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
148             for details.
149             </para>
150           </listitem>
151         </varlistentry>
152         <varlistentry>
153           <term><varname>Virtualization=</varname></term>
154           <listitem>
155             <para>Checks whether the system is executed in a virtualized
156             environment and optionally test whether it is a specific
157             implementation. See <literal>ConditionVirtualization=</literal> in
158             <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
159             for details.
160             </para>
161           </listitem>
162         </varlistentry>
163         <varlistentry>
164           <term><varname>KernelCommandLine=</varname></term>
165           <listitem>
166             <para>Checks whether a specific kernel command line option is
167             set (or if prefixed with the exclamation mark unset). See
168             <literal>ConditionKernelCommandLine=</literal> in
169             <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
170             for details.
171             </para>
172           </listitem>
173         </varlistentry>
174         <varlistentry>
175           <term><varname>Architecture=</varname></term>
176           <listitem>
177             <para>Checks whether the system is running on a specific
178             architecture. See <literal>ConditionArchitecture=</literal> in
179             <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
180             for details.
181             </para>
182           </listitem>
183         </varlistentry>
184       </variablelist>
185
186   </refsect1>
187
188   <refsect1>
189     <title>[Link] Section Options</title>
190
191     <para> The <literal>[Link]</literal> section accepts the following keys:</para>
192
193     <variablelist class='network-directives'>
194       <varlistentry>
195         <term><varname>MACAddress=</varname></term>
196         <listitem>
197           <para>The hardware address.</para>
198         </listitem>
199       </varlistentry>
200       <varlistentry>
201         <term><varname>MTUBytes=</varname></term>
202         <listitem>
203           <para>The maximum transmission unit in bytes to set for the
204           device. The usual suffixes K, M, G, are supported and are
205           understood to the base of 1024.</para>
206         </listitem>
207       </varlistentry>
208     </variablelist>
209   </refsect1>
210
211   <refsect1>
212     <title>[Network] Section Options</title>
213
214       <para>The <literal>[Network]</literal> section accepts the following keys:</para>
215
216       <variablelist class='network-directives'>
217         <varlistentry>
218           <term><varname>Description=</varname></term>
219           <listitem>
220             <para>A description of the device. This is only used for
221             presentation purposes.</para>
222           </listitem>
223         </varlistentry>
224         <varlistentry>
225           <term><varname>DHCP=</varname></term>
226           <listitem>
227             <para>Enables DHCPv4 and/or DHCPv6 support. Accepts
228             <literal>yes</literal>, <literal>no</literal>,
229             <literal>ipv4</literal>, or <literal>ipv6</literal>.</para>
230           </listitem>
231         </varlistentry>
232         <varlistentry>
233           <term><varname>DHCPServer=</varname></term>
234           <listitem>
235             <para>A boolean. Enables a basic DHCPv4 server on the
236             device. Mostly useful for handing out leases to container
237             instances.</para>
238           </listitem>
239         </varlistentry>
240         <varlistentry>
241           <term><varname>LinkLocalAddressing=</varname></term>
242           <listitem>
243             <para>Enables link-local address autoconfiguration. Accepts
244             <literal>yes</literal>, <literal>no</literal>,
245             <literal>ipv4</literal>, or <literal>ipv6</literal>. Defaults to
246             <literal>ipv6</literal>.</para>
247           </listitem>
248         </varlistentry>
249         <varlistentry>
250           <term><varname>IPv4LLRoute=</varname></term>
251           <listitem>
252             <para>A boolean. When true, sets up the route needed for
253             non-IPv4LL hosts to communicate with IPv4LL-only hosts. Defaults
254             to false.
255             </para>
256           </listitem>
257         </varlistentry>
258         <varlistentry>
259           <term><varname>IPv6Token=</varname></term>
260           <listitem>
261             <para>An IPv6 address with the top 64 bits unset. When set, indicates the
262             64 bits interface part of SLAAC IPv6 addresses for this link. By default
263             it is autogenerated.</para>
264           </listitem>
265         </varlistentry>
266         <varlistentry>
267           <term><varname>LLMNR=</varname></term>
268           <listitem>
269             <para>A boolean or <literal>resolve</literal>. When true, enables
270             Link-Local Multicast Name Resolution on the link, when set to
271             <literal>resolve</literal> only resolution is enabled, but not
272             announcement. Defaults to true.</para>
273           </listitem>
274         </varlistentry>
275         <varlistentry>
276           <term><varname>LLDP=</varname></term>
277           <listitem>
278             <para>A boolean. When true, enables LLDP link receive support.
279             </para>
280           </listitem>
281         </varlistentry>
282         <varlistentry>
283           <term><varname>BindCarrier=</varname></term>
284           <listitem>
285             <para>A port or a list of ports. When set, controls the
286             behaviour of the current interface. When all ports in the list
287             are in an operational down state, the current interface is brought
288             down. When at least one port has carrier, the current interface
289             is brought up.
290             </para>
291           </listitem>
292         </varlistentry>
293         <varlistentry>
294           <term><varname>Address=</varname></term>
295           <listitem>
296             <para>A static IPv4 or IPv6 address and its prefix length,
297             separated by a <literal>/</literal> character. Specify
298             this key more than once to configure several addresses.
299             The format of the address must be as described in
300             <citerefentry project='man-pages'><refentrytitle>inet_pton</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
301             This is a short-hand for an [Address] section only
302             containing an Address key (see below). This option may be
303             specified more than once.
304             </para>
305
306             <para>If the specified address is 0.0.0.0 (for IPv4) or
307             [::] (for IPv6), a new address range of the requested size
308             is automatically allocated from a system-wide pool of
309             unused ranges. The allocated range is checked against all
310             current network interfaces and all known network
311             configuration files to avoid address range conflicts. The
312             default system-wide pool consists of 192.168.0.0/16,
313             172.16.0.0/12 and 10.0.0.0/8 for IPv4, and fc00::/7 for
314             IPv6. This functionality is useful to manage a large
315             number of dynamically created network interfaces with the
316             same network configuration and automatic address range
317             assignment.</para>
318
319           </listitem>
320         </varlistentry>
321         <varlistentry>
322           <term><varname>Gateway=</varname></term>
323           <listitem>
324             <para>The gateway address, which must be in the format
325             described in
326             <citerefentry project='man-pages'><refentrytitle>inet_pton</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
327             This is a short-hand for a [Route] section only containing
328             a Gateway key. This option may be specified more than
329             once.</para>
330           </listitem>
331         </varlistentry>
332         <varlistentry>
333           <term><varname>DNS=</varname></term>
334           <listitem>
335             <para>A DNS server address, which must be in the format
336             described in
337             <citerefentry project='man-pages'><refentrytitle>inet_pton</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
338             This option may be specified more than once.</para>
339           </listitem>
340         </varlistentry>
341         <varlistentry>
342           <term><varname>Domains=</varname></term>
343           <listitem>
344             <para>The domains used for DNS resolution over this link.</para>
345           </listitem>
346         </varlistentry>
347         <varlistentry>
348           <term><varname>NTP=</varname></term>
349           <listitem>
350             <para>An NTP server address. This option may be specified more than once.</para>
351           </listitem>
352         </varlistentry>
353         <varlistentry>
354           <term><varname>IPForward=</varname></term>
355           <listitem><para>Configures IP forwarding for the network
356           interface. If enabled incoming packets on the network
357           interface will be forwarded to other interfaces according to
358           the routing table. Takes either a boolean argument, or the
359           values <literal>ipv4</literal> or <literal>ipv6</literal>,
360           which only enables IP forwarding for the specified address
361           family.</para></listitem>
362         </varlistentry>
363         <varlistentry>
364           <term><varname>IPMasquerade=</varname></term>
365           <listitem><para>Configures IP masquerading for the network
366           interface. If enabled packets forwarded from the network
367           interface will be appear as coming from the local host.
368           Takes a boolean argument. Implies
369           <varname>IPForward=yes</varname>.</para></listitem>
370         </varlistentry>
371         <varlistentry>
372           <term><varname>Bridge=</varname></term>
373           <listitem>
374             <para>The name of the bridge to add the link to.</para>
375           </listitem>
376         </varlistentry>
377         <varlistentry>
378           <term><varname>Bond=</varname></term>
379           <listitem>
380             <para>The name of the bond to add the link to.</para>
381           </listitem>
382         </varlistentry>
383         <varlistentry>
384           <term><varname>VLAN=</varname></term>
385           <listitem>
386             <para>The name of a VLAN to create on the link. This
387             option may be specified more than once.</para>
388           </listitem>
389         </varlistentry>
390         <varlistentry>
391           <term><varname>MACVLAN=</varname></term>
392           <listitem>
393             <para>The name of a MACVLAN to create on the link. This
394             option may be specified more than once.</para>
395           </listitem>
396         </varlistentry>
397         <varlistentry>
398           <term><varname>VXLAN=</varname></term>
399           <listitem>
400             <para>The name of a VXLAN to create on the link. This
401             option may be specified more than once.</para>
402           </listitem>
403         </varlistentry>
404         <varlistentry>
405           <term><varname>Tunnel=</varname></term>
406           <listitem>
407             <para>The name of a Tunnel to create on the link. This
408             option may be specified more than once.</para>
409           </listitem>
410         </varlistentry>
411       </variablelist>
412
413   </refsect1>
414
415   <refsect1>
416     <title>[Address] Section Options</title>
417
418       <para>An <literal>[Address]</literal> section accepts the
419       following keys. Specify several <literal>[Address]</literal>
420       sections to configure several addresses.</para>
421
422       <variablelist class='network-directives'>
423         <varlistentry>
424           <term><varname>Address=</varname></term>
425           <listitem>
426             <para>As in the <literal>[Network]</literal> section. This
427             key is mandatory.</para>
428           </listitem>
429         </varlistentry>
430         <varlistentry>
431           <term><varname>Peer=</varname></term>
432           <listitem>
433             <para>The peer address in a point-to-point connection.
434             Accepts the same format as the <literal>Address</literal>
435             key.</para>
436           </listitem>
437         </varlistentry>
438         <varlistentry>
439           <term><varname>Broadcast=</varname></term>
440           <listitem>
441             <para>The broadcast address, which must be in the format
442             described in
443             <citerefentry project='man-pages'><refentrytitle>inet_pton</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
444             This key only applies to IPv4 addresses. If it is not
445             given, it is derived from the <literal>Address</literal>
446             key.</para>
447           </listitem>
448         </varlistentry>
449         <varlistentry>
450           <term><varname>Label=</varname></term>
451           <listitem>
452             <para>An address label.</para>
453           </listitem>
454         </varlistentry>
455       </variablelist>
456   </refsect1>
457
458   <refsect1>
459     <title>[Route] Section Options</title>
460       <para>The <literal>[Route]</literal> section accepts the
461       following keys. Specify several <literal>[Route]</literal>
462       sections to configure several routes.</para>
463
464       <variablelist class='network-directives'>
465         <varlistentry>
466           <term><varname>Gateway=</varname></term>
467           <listitem>
468             <para>As in the <literal>[Network]</literal> section.</para>
469           </listitem>
470         </varlistentry>
471         <varlistentry>
472           <term><varname>Destination=</varname></term>
473           <listitem>
474             <para>The destination prefix of the route. Possibly
475             followed by a slash and the prefixlength. If omitted, a
476             full-length host route is assumed.</para>
477           </listitem>
478         </varlistentry>
479         <varlistentry>
480           <term><varname>Source=</varname></term>
481           <listitem>
482             <para>The source prefix of the route. Possibly followed by
483             a slash and the prefixlength. If omitted, a full-length
484             host route is assumed.</para>
485           </listitem>
486         </varlistentry>
487         <varlistentry>
488           <term><varname>Metric=</varname></term>
489           <listitem>
490             <para>The metric of the route. An unsigned integer</para>
491           </listitem>
492         </varlistentry>
493         <varlistentry>
494           <term><varname>Scope=</varname></term>
495           <listitem>
496             <para>The scope of the route. One of the values <literal>global</literal>,
497             <literal>link</literal> or <literal>host</literal>. Defaults to
498             <literal>global</literal>.</para>
499           </listitem>
500         </varlistentry>
501       </variablelist>
502   </refsect1>
503
504   <refsect1>
505     <title>[DHCP] Section Options</title>
506       <para>The <literal>[DHCP]</literal> section accepts the following keys:</para>
507
508       <variablelist class='network-directives'>
509         <varlistentry>
510           <term><varname>UseDNS=</varname></term>
511           <listitem>
512             <para>When true (the default), the DNS servers received
513             from the DHCP server will be used and take precedence over
514             any statically configured ones.</para>
515           </listitem>
516         </varlistentry>
517         <varlistentry>
518           <term><varname>UseMTU=</varname></term>
519           <listitem>
520             <para>When true, the interface maximum transmission unit
521             from the DHCP server will be used on the current link.
522             Defaults to false.</para>
523           </listitem>
524         </varlistentry>
525         <varlistentry>
526           <term><varname>SendHostname=</varname></term>
527           <listitem>
528             <para>When true (the default), the machine's hostname will be sent to the DHCP
529             server</para>
530           </listitem>
531         </varlistentry>
532         <varlistentry>
533           <term><varname>UseHostname=</varname></term>
534           <listitem>
535             <para>When true (the default), the hostname received from
536             the DHCP server will be used as the transient
537             hostname.</para>
538           </listitem>
539         </varlistentry>
540         <varlistentry>
541           <term><varname>UseDomains=</varname></term>
542           <listitem>
543             <para>When true (not the default), the domain name
544             received from the DHCP server will be used for DNS
545             resolution over this link.</para>
546           </listitem>
547         </varlistentry>
548         <varlistentry>
549           <term><varname>UseRoutes=</varname></term>
550           <listitem>
551             <para>When true (the default), the static routes will be
552             requested from the DHCP server and added to the routing
553             table with metric of 1024.</para>
554           </listitem>
555         </varlistentry>
556         <varlistentry>
557           <term><varname>CriticalConnection=</varname></term>
558           <listitem>
559             <para>When true, the connection will never be torn down
560             even if the DHCP lease expires. This is contrary to the
561             DHCP specification, but may be the best choice if, say,
562             the root filesystem relies on this connection. Defaults to
563             false.</para>
564           </listitem>
565         </varlistentry>
566         <varlistentry>
567           <term><varname>ClientIdentifier=</varname></term>
568           <listitem>
569             <para>DHCP client identifier to use. Either <literal>mac</literal>
570             to use the MAC address of the link or <literal>duid</literal>
571             (the default) to use a RFC4361-compliant Client ID.</para>
572           </listitem>
573         </varlistentry>
574         <varlistentry>
575           <term><varname>VendorClassIdentifier=</varname></term>
576           <listitem>
577             <para>The vendor class identifier used to identify vendor
578             type and configuration.</para>
579           </listitem>
580         </varlistentry>
581         <varlistentry>
582           <term><varname>RequestBroadcast=</varname></term>
583           <listitem>
584             <para>Request the server to use broadcast messages before
585             the IP address has been configured. This is necessary for
586             devices that cannot receive RAW packets, or that cannot
587             receive packets at all before an IP address has been
588             configured. On the other hand, this must not be enabled on
589             networks where broadcasts are filtered out.</para>
590           </listitem>
591         </varlistentry>
592         <varlistentry>
593           <term><varname>RouteMetric=</varname></term>
594           <listitem>
595             <para>Set the routing metric for routes specified by the
596             DHCP server.</para>
597           </listitem>
598         </varlistentry>
599            </variablelist>
600
601   </refsect1>
602
603   <refsect1>
604     <title>[Bridge] Section Options</title>
605       <para>The <literal>[Bridge]</literal> section accepts the
606       following keys.</para>
607       <variablelist class='network-directives'>
608         <varlistentry>
609           <term><varname>Cost=</varname></term>
610           <listitem>
611             <para>Each port in a bridge may have different speed. Cost
612             is used to decide which link to use. Faster interfaces
613             should have lower costs</para>
614           </listitem>
615         </varlistentry>
616       </variablelist>
617   </refsect1>
618
619   <refsect1>
620     <title>[BridgeFDB] Section Options</title>
621       <para>The <literal>[BridgeFDB]</literal> section manages the
622       forwarding database table of a port and accepts the following
623       keys. Specify several <literal>[BridgeFDB]</literal> sections to
624       configure several static MAC table entries.</para>
625
626       <variablelist class='network-directives'>
627         <varlistentry>
628           <term><varname>MACAddress=</varname></term>
629           <listitem>
630             <para>As in the <literal>[Network]</literal> section. This
631             key is mandatory.</para>
632           </listitem>
633         </varlistentry>
634         <varlistentry>
635           <term><varname>VLANId=</varname></term>
636           <listitem>
637             <para>The VLAN Id for the new static MAC table entry. If
638             omitted, no VLAN Id info is appended to the new static MAC
639             table entry.</para>
640           </listitem>
641         </varlistentry>
642       </variablelist>
643   </refsect1>
644
645   <refsect1>
646     <title>Example</title>
647     <example>
648       <title>/etc/systemd/network/50-static.network</title>
649
650       <programlisting>[Match]
651 Name=enp2s0
652
653 [Network]
654 Address=192.168.0.15/24
655 Gateway=192.168.0.1</programlisting>
656     </example>
657
658     <example>
659       <title>/etc/systemd/network/80-dhcp.network</title>
660
661       <programlisting>[Match]
662 Name=en*
663
664 [Network]
665 DHCP=yes</programlisting>
666     </example>
667
668     <example>
669       <title>/etc/systemd/network/bridge-static.network</title>
670
671       <programlisting>[Match]
672 Name=bridge0
673
674 [Network]
675 Address=192.168.0.15/24
676 Gateway=192.168.0.1
677 DNS=192.168.0.1</programlisting>
678     </example>
679
680     <example>
681       <title>/etc/systemd/network/bridge-slave-interface.network</title>
682
683       <programlisting>[Match]
684 Name=enp2s0
685
686 [Network]
687 Bridge=bridge0</programlisting>
688     </example>
689     <example>
690       <title>/etc/systemd/network/ipip.network</title>
691
692       <programlisting>[Match]
693 Name=em1
694
695 [Network]
696 Tunnel=ipip-tun</programlisting>
697     </example>
698
699     <example>
700       <title>/etc/systemd/network/sit.network</title>
701
702       <programlisting>[Match]
703 Name=em1
704
705 [Network]
706 Tunnel=sit-tun</programlisting>
707     </example>
708
709     <example>
710       <title>/etc/systemd/network/gre.network</title>
711
712       <programlisting>[Match]
713 Name=em1
714
715 [Network]
716 Tunnel=gre-tun</programlisting>
717     </example>
718
719     <example>
720       <title>/etc/systemd/network/vti.network</title>
721
722       <programlisting>[Match]
723 Name=em1
724
725 [Network]
726 Tunnel=vti-tun</programlisting>
727     </example>
728   </refsect1>
729
730   <refsect1>
731     <title>See Also</title>
732     <para>
733       <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
734       <citerefentry><refentrytitle>systemd-networkd</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
735       <citerefentry><refentrytitle>systemd.link</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
736       <citerefentry><refentrytitle>systemd.netdev</refentrytitle><manvolnum>5</manvolnum></citerefentry>
737     </para>
738   </refsect1>
739
740 </refentry>