A stable release of the interface for simplifying network configuration settings is now available — NetworkManager 1.40.0. Plugins for VPN support (Libreswan, OpenConnect, Openswan, SSTP, and others) are developed within their own development cycles.
Key innovations in NetworkManager 1.40:
- The command-line interface nmcli has implemented the "—offline" flag, allowing for the processing of connection profiles in keyfile format without contacting the NetworkManager background process. Specifically, when creating, displaying, deleting, and modifying settings bound to a network interface, the command "nmcli connection" can now operate without reaching out to the NetworkManager background process via D-Bus. For example, executing the command "nmcli —offline connection add …" will not send a request to the background process to add a connection profile, but will directly output the corresponding block of settings in keyfile format to stdout, enabling the use of nmcli in scripts for generating and modifying connection profiles. To activate the created profile, it can be saved in the directory /etc/NetworkManager/system-connections. # Configure file saving with permissions "600" (accessible only to the owner). umask 077 # Generate a profile in keyfile format. nmcli —offline connection add type ethernet con-name my-profile \ | tee /etc/NetworkManager/system-connections/my-profile.nmconnection # Modify the 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 rewriting the profile to disk, reload the NetworkManager settings nmcli connection reload
- Support for MPTCP (Multipath TCP) has been added, which is an extension of the TCP protocol that enables TCP connections to deliver packets simultaneously across multiple paths through different network interfaces bound to different IP addresses. NetworkManager can now manage the IP addresses announced or used in additional MPTCP streams, including automatically configuring those addresses, similar to what the mptcpd process does. NetworkManager also supports enabling MPTCP in the kernel by setting sysctl /proc/sys/net/mptcp/enabled and configuring limits defined by the command 'ip mptcp limits'. A new property 'connection.mptcp-flags' has been introduced to manage MPTCP processing, allowing MPTCP to be enabled and destination address options to be selected (signal, subflow, backup, fullmesh). By default, MPTCP is automatically enabled in NetworkManager if sysctl /proc/sys/net/mptcp/enabled is set in the kernel.
- Binding parameters recording (the key to connect to is specified, and iroh finds the associated host and establishes an encrypted connection using the QUIC protocol). Direct P2P connections are established whenever possible, but if not, it falls back to using relays, which are also employed for host discovery by keys. You can run your own relay or connect to public relays supported by the community. for DHCP (DHCP lease) is provided in the file /run/NetworkManager/devices/$IFINDEX (information is stored in the [dhcp4] and [dhcp6] sections), which allows bindings to be determined through simple file reading without calling D-Bus or executing the 'nmcli -f all device show eth0' command.
- The connection profile has been updated to include the ipv4.link-local parameter for binding local IPv4 links with intranet addresses 169.254.0.0/16 (IPv4LL, Link-local). Previously, IPv4LL addresses could be specified either manually (ipv4.method=link-local) or obtained via DHCP.
- The 'ipv6.mtu' parameter has been added for configuring MTU (Maximum Transmission Unit) for IPv6.
- The code for the unused DHCPv4 client implementation, based on systemd code, has been removed. The n-dhcp4 implementation from the nettools package has long been used as the DHCP client.
- DHCP is ensured to restart when the MAC address on the device changes.
Source: opennet.ru
