NetworkManager has been, for years, the epicenter of network management in Linux-based operating systems. Each new version introduces improvements and, above all, expands compatibility and stability, which are so crucial in both home and business environments. This time, the latest version has been released. Network Manager 1.54, bringing with it a series of advanced features and interesting tweaks that are generating buzz in the open source community. If you're interested in keeping your system up-to-date or just want to stay on top of the latest developments, here you'll find a detailed and easy-to-understand explanation of this latest version.
When we talk about NetworkManager 1.54, we talk about one of the most widely used network management tools today. Not only is it the default manager in many GNU/Linux distributions, but it also continues to lead the way in implementing connectivity, security, and flexibility standards. Therefore, a thorough understanding of the new features, changes, and dependencies in this version is a must for administrators, enthusiasts, and anyone who wants to get the most out of their network.
NetworkManager 1.54 Highlights
The new release of NetworkManager 1.54 comes just five months after the version 1.52 and lands in the repositories as the latest stable release. What's new under the hood? For starters, support has been added for configuring IPv4 forwarding per device, using the connection property. ipv4.forwarding. This allows for granular management how packet forwarding is handled on different interfaces, providing greater flexibility in complex or multi-subnet environments.
Another essential novelty lies in the Extended support for cloud environments, especially on OCI baremetal via nm-cloud-setup, This facilitates automated network deployment and configuration in these increasingly popular environments. In addition, interfaces can now be configured. loopback through the text-based user interface (NMTUI), which is highly sought after by those who manage servers remotely or prefer tools without a graphical interface.
In IPv6, NetworkManager 1.54 brings with it the new “prefix-delegation” configuration. This function allows you to specify using the property subnet-id The subnet to use on the downstream interface when using prefix delegation. This It is especially relevant in environments where IPv6 is used intensively., facilitating the administration and assignment of subnets in an automated and efficient manner.
Also, this version introduces a new parameter for OVS DPDK interfaces: the property ovs-dpdk.lsc-interrupt It allows you to define the link state detection mode (LSC) in this type of interfaces, thus incorporating another option for the advanced management of virtualized networks optimized for high performance.
Improvements in security, startup support, and compatibility
NetworkManager 1.54 not only focuses on flexibility, but also strengthens security and integration with system boot. Now, systemd adds services intended to provide network connectivity to the initrd environment, during the early stages of system boot. This addition is key for systems that require early connectivity, such as servers that mount network volumes or deploy images from the cloud.
Safety is not left aside either. The ability to automatically create firewall rules when enabling a WireGuard connection to a node with IPv6 has been implemented., to ensure that received packets aren't dropped by default due to the kernel's reverse path filtering. This way, users can establish secure and functional VPN tunnels without any additional complications.
A curious detail for those working with new storage technologies: NetworkManager You can now analyze the NVMe Boot Firmware Table (NBFT) using the initrd generator, which allows you to configure the network even before the operating system is fully operational. This is especially useful in enterprise environments or servers booting from NVMe devices.
Dynamic configurations and advanced flexibility
One of the most interesting additions is the your property sriov.preserve-on-down. This setting allows you to decide whether NetworkManager should retain the SR-IOV parameters on the device when the connection is disconnected or restore the default values. This feature is essential in environments that use network functions virtualization and require precise management of hardware resources.
Another significant improvement is the Possibility of hot-resetting most ovs-bridge and ovs-port connection parameters without having to interrupt the connection, allowing adjustments and maintenance to be made on virtualized or complex networks without any inconvenience to users or unforeseen downtime.
Things to consider before upgrading or installing NetworkManager 1.54
Before you jump into installing or upgrading to version 1.54, consider the following key points:
- Check that your operating system includes or is compatible with all required dependencies, as the absence of any can cause failures in the management of certain functions.
- Consider whether you need new features, such as support for WireGuard or advanced virtual interface configuration, which are especially useful in modern environments, hybrid networks, or infrastructures requiring high availability and security.
- Check for compatibility with tools and scripts you've already used in your previous deployments. There may be slight differences in options and commands, so a quick test in a staging environment is always a good idea before making the final jump.
Keep in mind that, despite this being a stable and well-tested update, it's common for minor bugs or occasional incompatibilities to appear after a recent release. Therefore, it is advisable to review the changelogs included in the official source tarball and keep an eye on the forums and mailing lists of the respective projects.
Those looking for more flexible, secure, and modern network management will find NetworkManager 1.54 a top-notch option. Now that you know the details of its new features, the requirements, and the deployment process, you have all the tools you need to make the best decision for your work or testing environment.
More information in your GitLab.
