Recientemente the release of the new version of the stable interface was published to simplify the network configuration "NetworkManager 1.20", version in which a handful of innovations have been added but above all it comes with bug fixes and greater support.
NetworkManager is a utility takes an opportunistic approach to network selection, trying to use the best available connection when outages occur, or when the user moves between wireless networks. You prefer Ethernet connections over "known" wireless networks. The user is prompted for WEP or WPA keys, as required.
NetworkManager has two components:
- a service that manages connections and reports of changes in the network.
- a graphical desktop application that allows the user to manipulate network connections. The nmcli applet provides similar functionality on the command line.
On the other hand plug-ins to support VPN, OpenConnect, PPTP, OpenVPN, and OpenSWAN are developed as part of their own development cycles.
Plugins to support VPN, OpenConnect, PPTP, OpenVPN, and OpenSWAN are developed as part of their own development cycles.
Main new features of NetworkManager 1.20
In this new version configuration management plugin deployment changed and the method of storing profiles on disk. Added support for migrating connection profiles between plugins.
The stored profiles in memory of now they are processed only by the keyfile plugin and saved in the / run directory, which prevents loss of profiles after restarting NetworkManager and enables the use of the FS-based API to create profiles in memory.
Along with this, it also highlights the cleaned out obsolete components within the utility. In particular, the libnm-glib library was removed, which was replaced by the libnm library in NetworkManager 1.0, the ibft plugin was removed (initrd's nm-initrd-generator should be used to transfer network configuration data from firmware), and support for "main.monitor- connection files" in NetworkManager.conf (you must explicitly call "nmcli connection load" or "nmcli connection reload").
By default, the built-in DHCP client is enabled ("internal" mode) instead of the previously used dhclient application. You can change the default by using the assembly option "–with-config-dhcp-default" or by setting the main.dhcp in the configuration file.
On the other hand, there is a new method D-Bus AddConnection2 (), which allows you to block the automatic connection of the profile at the time of its creation.
The "do not reapply" flag has been added to the Update2 () method, in which changing the content of the connection profile does not automatically change the actual device settings until the profile is reactivated.
While for different distributions, the ability to place dispatch scripts in the / usr / lib / NetworkManager directory is provided, which can be used on system images that are available in read-only mode and clean / etc every time it starts.
Of the other changes that stand out in this new version we can find:
- Added "ipv6.method = disabled" setting, which allows you to disable IPv6 for the device.
- Added support for wireless mesh networks, each node in which is connected through neighboring nodes
- Added ability to configure fq_codel (Fair Queue Controlled Delay) packet queuing discipline and mirrored action to reflect traffic
- In libnm, the code for parsing the configuration in JSON format has been modified and provides stricter parameter checking.
- Support for the "suppress_prefixlength" attribute is added in routing rules to the source address (policy routing).
- WireGuard VPN has script support to automatically assign the default route "wireguard.ip4-auto-default-route" and "wireguard.ip6-auto-default-route".
How to get NetworkManager 1.20.0?
For those interested in being able to obtain this new version of NetworkManager 1.20.0, you should know that at the moment there are no packages built for Ubuntu or derivatives. So if you want to get this version they must build NetworkManager 1.20.0 from source code.