X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-networkd.service.xml;h=13443257823aac02feb8549e9b242ff5b812ecea;hb=763e20e675799e9c8d8b62857cdd01126b62e9a9;hp=8bf2d928b28b0d593e328bc8694f33e2600749b8;hpb=6ae115c1fe95611b39d2f20cfcea3d385429f59e;p=elogind.git
diff --git a/man/systemd-networkd.service.xml b/man/systemd-networkd.service.xml
index 8bf2d928b..134432578 100644
--- a/man/systemd-networkd.service.xml
+++ b/man/systemd-networkd.service.xml
@@ -58,7 +58,8 @@
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.
Network configurations applied before networkd is started
are not removed, and configuration applied by networkd are not
@@ -68,118 +69,148 @@
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,
+ All configuration 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
+ system-supplied configuration file with a local file if needed; a symlink in
+ /etc with the same name as a configuration 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
- .
-
-
-
-
- The [Address] section accepts the following keys:
-
-
-
- Address
-
- As in the [Network] section.
-
-
-
- Label
-
- An address label.
-
-
-
+ disables the configuration file entirely.
+
+ Virtual Network Devices
+ Netdev files must have the extension .netdev;
+ other extensions are ignored. Virtual network devices are created as soon
+ as networkd is started.
+
+ The [Bridge] section accepts the following
+ keys:
+
+
+
+ Name
+
+ The interface name used when creating the
+ bridge. This option is compulsory.
+
+
+
+
+
+ Networks
+ Network files must have the extension .network;
+ other extensions are ignored. Networks are applied to links whenever the links
+ appear.
+
+ 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
+ .
+
+
+
+ Bridge
+
+ The name of the bridge to add the configured link to.
+
+
+
+
+ The [Address] section accepts the following keys:
+
+
+
+ Address
+
+ As in the [Network] section.
+
+
+
+ Label
+
+ An address label.
+
+
+
+