X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd-networkd.service.xml;h=05707988785620f47dcfd3fa78b98cd666bb6a09;hp=f3239bbf9428b34c1e7951453689fd5f4be8c973;hb=091a364c802e34a58f3260c9cb5db9b75c62215c;hpb=002f5de9a9d3f04982588433895dca9faa2c0f22
diff --git a/man/systemd-networkd.service.xml b/man/systemd-networkd.service.xml
index f3239bbf9..057079887 100644
--- a/man/systemd-networkd.service.xml
+++ b/man/systemd-networkd.service.xml
@@ -58,118 +58,44 @@
systemd-networkd is a system
service that manages networks. It detects and configures
- network devices as they appear.
+ network devices as they appear, as well as creating virtual
+ network devices.
+
+ To configure low-level link settings independently of
+ networks, see
+ systemd.link5.
Network configurations applied before networkd is started
- are not removed, and configuration applied by networkd are not
- removed when networkd exits. This ensures restarting networkd
- does not cut the network connection, and in particular that it
- is safe to transition between the initrd and the real root,
+ are not removed, and static configuration applied by networkd
+ is not removed when networkd exits. Dynamic configuration applied by
+ networkd may also optionally be left in place on shutdown. This ensures
+ restarting networkd does not cut the network connection, and, in particular,
+ that it is safe to transition between the initrd and the real root,
and back.
- Network Configuration
- The network files are read from the files located in the
+ Configuration Files
+ The configuration files are read from the files located in the
system network directory /usr/lib/systemd/network,
the volatile runtime network directory
/run/systemd/network and the local administration
- network directory /etc/systemd/network.
- All link files are collectively sorted and processed in lexical order,
- regardless of the directories in which they live. However, files with
- identical filenames replace each other. Files in
- /etc have the highest priority, files in
- /run take precedence over files with the same
- name in /lib. This can be used to override a
- system-supplied network file with a local file if needed; a symlink in
- /etc with the same name as a network file in
- /lib, pointing to /dev/null,
- disables the network file entirely. Network files must have the extension
- .network; other extensions are ignored.
-
- The network file contains a [Match] section,
- which determines if a given network file may be applied to a given device;
- and a [Network] section specifying how the device should
- be configured. The first (in lexical order) of the network files that
- matches a given device is applied.
-
- A network file is said to match a device if each of the entries in the
- [Match] section matches, or if the section is empty.
- The following keys are accepted:
-
-
-
- MACAddress
-
- The hardware address.
-
-
-
- Path
-
- The persistent path, as exposed by the udev
- property ID_PATH.
-
-
-
- Driver
-
- The driver currently bound to the device, as
- exposed by the udev property DRIVER.
-
-
-
-
- Type
-
- The device type, as exposed by the udev property
- DEVTYPE.
-
-
-
- Name
-
- The device name, as exposed by the udev property
- INTERFACE.
-
-
-
-
- The [Network] section accepts the following keys:
-
-
-
- Description
-
- A description of the device. This is only used for
- presentation purposes.
-
-
-
- Address
-
- A static IPv4 or IPv6 address and its prefix length,
- separated by a '/' character. The format of the address must
- be as described in
- inet_pton3
- .
-
-
-
- Gateway
-
- The gateway address, which must be in the format described in
- inet_pton3
- .
-
-
-
+ network directory /etc/systemd/network.
+
+ Networks are configured in .network files, see
+ systemd.network5,
+ and virtual network devices are configured in .netdev files, see
+ systemd.netdev5.
+
See Also
systemd1,
- udev7,
+ systemd.link5,
+ systemd.network5,
+ systemd.netdev5,
+ systemd-network-wait-online.service8