{"id":119503,"date":"2024-08-15T21:43:01","date_gmt":"2024-08-15T19:43:01","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-netplan-1-1-instrumentariya-dlya-nastrojki-parametrov-seti"},"modified":"2024-08-15T21:43:01","modified_gmt":"2024-08-15T19:43:01","slug":"vypusk-netplan-1-1-instrumentariya-dlya-nastrojki-parametrov-seti","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-netplan-1-1-instrumentariya-dlya-nastrojki-parametrov-seti","title":{"rendered":"Release of Netplan 1.1, a tool for configuring network parameters","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of tool Netplan 1.1 has been announced, which enhances the format for storing network interface settings and associated utilities for managing network configurations. Netplan allows for the storage of parameters in YAML format and provides backends that abstract access to configuration for NetworkManager and systemd-networkd. This tool is used in the Ubuntu distribution starting from release 17.10 and in Debian 12 builds for cloud systems. The project is developed by Canonical with contributions from employees of Microsoft and Deutsche Telekom. The project's code is written in Python and C and is distributed under the GPLv3 license. <\/p>\n
The operation of netplan involves reading network settings from files in the format \"{lib,etc,run}\/netplan\/*.yaml\" during the boot process and writing the configuration to the \/run directory in a format suitable for further processing by systemd-networkd or NetworkManager. All configuration is stored solely in the original YAML file without using \"\/etc\/network\/interfaces\", allowing for the separation of configurations into multiple files, for example, to extract settings for libvirt and lxd into separate files. The parameters of network interfaces are defined using a declarative syntax that makes it relatively straightforward to describe the structure of a complex network. <\/p>\n
Unlike the ifupdown format, Netplan uses a declarative syntax; it supports the application of masks for network interface names, MAC addresses, drivers, and other components. When parsing the hierarchy of network interface parameters, context is considered, which allows the correct and orderly transfer of settings to handlers (in ifupdown, parsing complex configurations may encounter issues due to race conditions). <\/p>\n
In the new release: <\/p>\n
\n
The ability to override the logic of the systemd-networkd-wait-online service to wait for specific internal (link-local) and routable (with routable state) network interfaces.\n
Support for changing settings for the embedded-switch-mode for network interfaces without virtual functions (VF, virtual-function) on SR-IOV (Single Root I\/O Virtualization) devices.\n
Support for flags that allow influencing the configuration parser to ignore certain incorrect settings without stopping the generation of the entire backend configuration.\n
Corrections have been made to resolve issues specific to ProtonVPN and Microsoft Azure Linux. <\/ul>\n