2013-11-10 23:52:53 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
2019-03-14 16:40:58 +03:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
2015-06-18 20:47:44 +03:00
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2020-11-09 07:23:58 +03:00
<!-- SPDX - License - Identifier: LGPL - 2.1 - or - later -->
2013-11-10 23:52:53 +04:00
2013-11-13 01:44:18 +04:00
<refentry id= "systemd-networkd.service" conditional= 'ENABLE_NETWORKD' >
2013-11-10 23:52:53 +04:00
2015-02-04 05:14:13 +03:00
<refentryinfo >
<title > systemd-networkd.service</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > systemd-networkd.service</refentrytitle>
<manvolnum > 8</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd-networkd.service</refname>
<refname > systemd-networkd</refname>
<refpurpose > Network manager</refpurpose>
</refnamediv>
<refsynopsisdiv >
<para > <filename > systemd-networkd.service</filename> </para>
2015-06-18 20:47:44 +03:00
<para > <filename > /usr/lib/systemd/systemd-networkd</filename> </para>
2015-02-04 05:14:13 +03:00
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > <command > systemd-networkd</command> is a system service that
manages networks. It detects and configures network devices as
they appear, as well as creating virtual network devices.</para>
<para > To configure low-level link settings independently of
networks, see
<citerefentry > <refentrytitle > systemd.link</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .</para>
2017-09-15 12:23:57 +03:00
<para > <command > systemd-networkd</command> will create network devices based
on the configuration in
<citerefentry > <refentrytitle > systemd.netdev</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
files, respecting the [Match] sections in those files.</para>
<para > <command > systemd-networkd</command> will manage network addresses and
routes for any link for which it finds a <filename > .network</filename> file
with an appropriate [Match] section, see
<citerefentry > <refentrytitle > systemd.network</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
For those links, it will flush existing network addresses and routes when
bringing up the device. Any links not matched by one of the
<filename > .network</filename> files will be ignored. It is also possible to
explicitly tell <filename > systemd-networkd</filename> to ignore a link by
using <varname > Unmanaged=yes</varname> option, see
<citerefentry > <refentrytitle > systemd.network</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
</para>
<para > When <filename > systemd-networkd</filename> exits, it generally leaves
existing network devices and configuration intact. This makes it possible to
2018-10-29 20:28:11 +03:00
transition from the initramfs and to restart the service without breaking
2017-09-15 12:23:57 +03:00
connectivity. This also means that when configuration is updated and
<filename > systemd-networkd</filename> is restarted, netdev interfaces for
which configuration was removed will not be dropped, and may need to be
cleaned up manually.</para>
2020-03-05 10:20:31 +03:00
<para > <command > systemd-networkd</command> may be introspected and controlled at runtime using
<citerefentry > <refentrytitle > networkctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> .
</para>
2015-02-04 05:14:13 +03:00
</refsect1>
<refsect1 > <title > Configuration Files</title>
<para > The configuration files are read from the files located in the
2015-06-18 20:47:44 +03:00
system network directory <filename > /usr/lib/systemd/network</filename> ,
2015-02-04 05:14:13 +03:00
the volatile runtime network directory
<filename > /run/systemd/network</filename> and the local administration
2015-06-18 20:47:44 +03:00
network directory <filename > /etc/systemd/network</filename> .</para>
2015-02-04 05:14:13 +03:00
<para > Networks are configured in <filename > .network</filename>
files, see
<citerefentry > <refentrytitle > systemd.network</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
and virtual network devices are configured in
<filename > .netdev</filename> files, see
<citerefentry > <refentrytitle > systemd.netdev</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
</para>
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
2020-03-05 10:20:31 +03:00
<citerefentry > <refentrytitle > networkctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2015-02-04 05:14:13 +03:00
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.link</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.network</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.netdev</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2020-03-05 10:05:24 +03:00
<citerefentry > <refentrytitle > systemd-networkd-wait-online.service</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
2020-06-25 15:38:21 +03:00
<citerefentry > <refentrytitle > systemd-network-generator.service</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry>
2015-02-04 05:14:13 +03:00
</para>
</refsect1>
2013-11-10 23:52:53 +04:00
</refentry>