Section: systemd.network (5)
Network files must have the extension .network; other extensions are ignored. Networks are applied to links whenever the links appear.
The .network files are read from the files located in the system network directory /lib/systemd/network, the volatile runtime network directory /run/systemd/network and the local administration network directory /etc/systemd/network. 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 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 configuration file entirely.
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:
The "[Network]" section accepts the following keys:
:A static IPv4 or IPv6 address and its prefix length, separated by a "/" character. Specify this key more than once to configure several addresses. The format of the address must be as described in inet_pton?(3). This is a short-hand for an [Address] section only containing an Address key (see below). This option may be specified more than once.
If the specified address is 0.0.0.0 (for IPv4) or [::] (for IPv6), a new address range of the requested size is automatically allocated from a system-wide pool of unused ranges. The allocated range is checked against all current network interfaces and all known network configuration files to avoid address range conflicts. The default system-wide pool consists of 192.168.0.0/16, 172.16.0.0/12 and 10.0.0.0/8 for IPv4, and fc00::/7 for IPv6. This functionality is useful to manage a large number of dynamically created network interfaces with the same network configuration and automatic address range assignment.
An "[Address]" section accepts the following keys. Specify several "[Address]" sections to configure several addresses.
The "[Route]" section accepts the following keys. Specify several "[Route]" sections to configure several routes.
The "[DHCP]" section accepts the following keys:
Example 1. /etc/systemd/network/50-static.network
[Match] Name=enp2s0 [Network] Address=192.168.0.15/24 Gateway=192.168.0.1
Example 2. /etc/systemd/network/80-dhcp.network
[Match] Name=en* [Network] DHCP=yes
Example 3. /etc/systemd/network/bridge-static.network
[Match] Name=bridge0 [Network] Address=192.168.0.15/24 Gateway=192.168.0.1 DNS=192.168.0.1
Example 4. /etc/systemd/network/bridge-slave-interface.network
[Match] Name=enp2s0 [Network] Bridge=bridge0
Example 5. /etc/systemd/network/ipip.network
[Match] Name=em1 [Network] Tunnel=ipip-tun
Example 6. /etc/systemd/network/sit.network
[Match] Name=em1 [Network] Tunnel=sit-tun
Example 7. /etc/systemd/network/gre.network
[Match] Name=em1 [Network] Tunnel=gre-tun
Example 8. /etc/systemd/network/vti.network
[Match] Name=em1 [Network] Tunnel=vti-tun
Tutoriais de Tecnologia Web