NetworkManager 1.58.1 has been released as the latest update to the widely used Linux network management service.
One notable change concerns WPA3 networks. The new release fixes automatic connection to SAE-based WPA3 networks using profiles configured with key-mgmt=wpa-psk, addressing cases where NetworkManager failed to reconnect automatically.
Another fix ensures IPv4 forwarding is properly enabled on mobile broadband data interfaces. NetworkManager also now performs connectivity checks when an interface has only an IPv4 link-scope default route.
DNS handling also received several fixes. NetworkManager now ignores unspecified addresses received as DNS nameservers through RDNSS and DHCPv6 and skips invalid nameservers when configuring systemd-resolved.
Moreover, the port number specified for a DNS server in DNS URIs is now correctly forwarded to systemd-resolved, fixing situations where non-default DNS ports could be lost during configuration.
On the DHCP side, NetworkManager logs a warning when it ignores DHCPv4 option 3 (router) because classless static routes from option 121 or 249 are present but leave the connection without a gateway.
NetworkManager 1.58.1 introduces stricter handling for private 802.1X connection profiles. For connections specifying a user through the connection.permissions property, the ca-path and phase2-ca-path settings are no longer accepted.
Elsewhere, the initrd generator sets the parent interface by name for NBFT VLAN connections, avoiding potential race conditions during boot. Bluetooth NAP connection normalization has also been fixed.
Finally, NetworkManager 1.58.1 addresses multiple crashes, although the upstream notes do not provide further details about the individual cases.
For more details, see the changelog. NetworkManager 1.58.1 is now available from the project’s GitLab repository, where you can download source tarballs and accompanying release assets.
