INFRA Signal 429
NetworkManager 1.58.1 fixes WPA3 auto-connect, modem IPv4 forwarding, and DNS handling bugs
↗
NetworkManager 1.58.1 resolves issues with WPA3 reconnection, IPv4 forwarding on modems, DNS configuration, and multiple crashes in Linux network management.
Engineers managing Linux network stacks will see fewer manual reconnection failures on WPA3 networks and more reliable DNS and modem behavior. The fixes reduce edge-case failures that previously required workarounds or manual intervention.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
WPA3 auto-connect now works for profiles using key-mgmt=wpa-psk after SAE authentication failures
IPv4 forwarding is enforced on mobile broadband interfaces and connectivity checks run with IPv4 link-scope routes
DNS handling ignores unspecified RDNSS/DHCPv6 nameservers and preserves non-default port numbers in URIs
THE READ
What the cluster adds up to.
NetworkManager 1.58.1 targets specific failure modes in enterprise and mobile Linux deployments. The WPA3 auto-connect fix eliminates a silent failure where profiles configured for WPA-PSK would not reconnect after an SAE authentication timeout. This affects laptops and IoT devices that roam between access points without user intervention. The change requires no configuration update, but operators should verify that existing profiles with key-mgmt=wpa-psk now reconnect without manual triggers.
Modem and DNS reliability improvements address edge cases that previously required manual overrides. IPv4 forwarding on mobile broadband interfaces is now enforced, preventing dropped traffic when the interface is the default route. DNS fixes ignore malformed RDNSS/DHCPv6 responses and preserve non-standard port numbers, reducing silent failures in split-horizon or custom DNS setups. These changes are transparent to most users but may expose misconfigured networks that relied on NetworkManager’s previous leniency.
The release tightens security for 802.1X profiles by rejecting ca-path settings when a user is specified via connection.permissions. This prevents potential privilege escalation via certificate path manipulation but may break existing profiles that mixed user permissions with system-wide CA paths. The initrd generator now sets parent interfaces by name for NBFT VLANs, avoiding race conditions during boot, though this only affects systems using network boot with VLAN tagging. Undocumented crash fixes suggest stability improvements, but the lack of detail makes targeted testing difficult.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER