RouteMetric=100 /etc/systemd/network/work Note: The Metric option is for static routes while the RouteMetric option is for setups not using static routes. Systemd-networkd does not set per-interface-type default route metrics, so it needs to be configured manually: If one of the connections is terminated, the other automatically wins without there being a gap with nothing configured (ongoing transfers may still not deal with this nicely but that is at a different OSI layer). To break the tie, the kernel uses the metric. This will be the case when both wireless and wired devices on the system have active connections. The kernel's route metric (same as configured with ip) decides which route to use for outgoing packets, in cases when several match. This way, no connection downtime is observed when the wired connection is unplugged. This setup will enable a DHCP IP for both a wired and wireless connection making use of the metric directive to allow the kernel to decide on-the-fly which one to use. Wired and wireless adapters on the same machine To authenticate to the wireless network, use e.g. Tip: IgnoreCarrierLoss=3s ensures that systemd-networkd will not re-configure the interface (e.g., release and re-acquire a DHCP lease) for a short period (3 seconds in this example) while the wireless interface roams to another access point within the same wireless network (SSID), which translates to shorter downtime when roaming. If the wireless adapter has a static IP address, the configuration is the same (except for the interface name) as in a wired adapter. In order to connect to a wireless network with systemd-networkd, a wireless adapter configured with another application such as wpa_supplicant or iwd is required. See #network files or work(5) for more options. Wired adapter using DHCP /etc/systemd/network/work ĭHCP=yes Wired adapter using a static IP /etc/systemd/network/work Īddress= can be used more than once to configure multiple IPv4 or IPv6 addresses.

To disable IPv6, see IPv6#systemd-networkd.

To exclude them, use Type=ether in combination with Kind=!*.

Note that Type=ether will also match virtual Ethernet interfaces.

Type=ether for Ethernet, Type=wlan for Wi-Fi and Type=wwan for WWAN.

Devices can also be matched by their type.

It is also possible to use a wildcard, e.g.

See Network configuration#Network interfaces for checking your adapter names. These names can be different on different systems.

In the examples below, enp1s0 is the wired adapter and wlp2s0 is the wireless adapter.

The options specified in the configuration files are case sensitive.

For example, to wait for enp1s0, disable rvice and enable systemd-networkd-wait-online(8) for details. etc/systemd/system//nf ĮxecStart=/usr/lib/systemd/systemd-networkd-wait-online -anyĪlternatively, use to wait for a specific interface. To change the behaviour to wait for any interface rather than all interfaces to become online, edit the service and add the -any parameter to the ExecStart line: This may cause an unwanted delay in the startup process. if a dual-port Ethernet card, but only one cable plugged in), starting rvice will fail after the default timeout of 2 minutes. See also systemd#Running services after the network is up.īy default, rvice waits for all links managed by systemd-networkd to be fully configured or failed, and for at least one link to be online.įor system with multiple network interfaces that are not expected to be connected all the time (e.g. The latter has WantedBy=network-online.target, so it will be started only when network-online.target itself is enabled or pulled in by some other unit.

(Discuss in Talk:Systemd-networkd)Įnabling rvice also enables rvice, which is a oneshot system service that waits for the network to be configured. Reason: Per rvice(8), 'online means that the link's operational state is equal or higher than 'degraded'.'Īdd instructions for setting RequiredForOnline=routable in. Note that systemd-resolved can also be used without systemd-networkd.(by setting ( DHCP= and/or IPv6AcceptRA= in the section, and UseDNS=yes (the default) in the corresponding section(s), ,, see work(5)). systemd-resolved is also required to obtain DNS addresses from DHCP servers or IPv6 router advertisements.systemd-resolved is required if DNS entries are specified in.It is important to understand how nf and systemd-resolved interact to properly configure the DNS that will be used, some explanations are provided in systemd-resolved.It is optional to also configure systemd-resolved, which is a network name resolution service to local applications, considering the following points:

Find a list of the currently running services with systemctl -type=service and then stop them. Note: Ensure that no other service that wants to configure the network is running in fact, multiple networking services will conflict.

Archlinux networkmanager