A stable release of the interface is available to simplify network settings - NetworkManager 1.40.0. Plugins for VPN support (Libreswan, OpenConnect, Openswan, SSTP, etc.) are developed within their own development cycles.
Key innovations in NetworkManager 1.40:
- The nmcli command-line interface implements the "--offline" flag, which allows processing connection profiles in keyfile format without calling the NetworkManager background process. In particular, when creating, displaying, deleting and changing settings associated with a network interface, the "nmcli connection" command can now work without accessing the NetworkManager background process via D-Bus. For example, when executing the βnmcli βoffline connection add β¦β command, the nmcli utility will not send a request to the background process to add a connection profile, but will directly output the corresponding settings block in keyfile format to stdout, which allows using nmcli in scripts to generate and modify connection profiles . For activation, the created profile can be saved in the /etc/NetworkManager/system-connections directory. # Set up saving files with permissions "600" (only available to the owner). umask 077 # Generate profile in keyfile format. nmcli --offline connection add type ethernet con-name my-profile \ | tee /etc/NetworkManager/system-connections/my-profile.nmconnection # Change profile nmcli --offline connection modify connection.mptcp-flags enabled,signal \ < /etc/NetworkManager/system-connections/my-profile.nmconnection \ | tee /etc/NetworkManager/system-connections/my-profile.nmconnection~ mv /etc/NetworkManager/system-connections/my-profile.nmconnection~ \ /etc/NetworkManager/system-connections/my-profile.nmconnection # After overwriting profile on disk reload NetworkManager settings nmcli connection reload
- Added support for MPTCP (Multipath TCP), an extension of the TCP protocol for organizing the operation of a TCP connection with the delivery of packets simultaneously along several routes through different network interfaces bound to different IP addresses. NetworkManager can now manage the IP addresses advertised or used in additional MPTCP flows, including configuring these addresses automatically, similar to how the mptcpd process does. NetworkManager also supports enabling MPTCP in the kernel by setting sysctl /proc/sys/net/mptcp/enabled and setting the limits set by the "ip mptcp limits" command. To control MPTCP processing, a new property "connection.mptcp-flags" has been proposed, through which you can enable MPTCP and select address assignment parameters (signal, subflow, backup, fullmesh). By default, MPTCP is automatically enabled in NetworkManager if sysctl /proc/sys/net/mptcp/enabled is set in the kernel.
- Recording of IP address binding parameters for DHCP (DHCP lease) is provided in the /run/NetworkManager/devices/$IFINDEX file (information is stored in sections [dhcp4] and [dhcp6]), which allows you to determine bindings by simply reading the file without accessing D -Bus or running the "nmcli -f all device show eth0" command.
- The ipv4.link-local parameter has been added to the connection profile to bind local IPv4 links with intranet addresses 169.254.0.0/16 (IPv4LL, Link-local). Previously, IPv4LL addresses could either be specified manually (ipv4.method=link-local) or obtained via DHCP.
- Added "ipv6.mtu" parameter to configure MTU (Maximum Transmission Unit) for IPv6.
- Removed code from an unused DHCPv4 client implementation based on code from systemd. The n-dhcp4 implementation from the nettools package has long been used as a DHCP client.
- Provided DHCP restart when changing the MAC address on the device.
Source: opennet.ru