Bug 2077392
Summary: | [Rebase] Rebase NetworkManager to last stable release | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Thomas Haller <thaller> |
Component: | NetworkManager | Assignee: | Vojtěch Bůbela <vbubela> |
Status: | CLOSED ERRATA | QA Contact: | Vladimir Benes <vbenes> |
Severity: | unspecified | Docs Contact: | Marc Muehlfeld <mmuehlfe> |
Priority: | unspecified | ||
Version: | 9.1 | CC: | acabral, bgalvani, ferferna, lrintel, rkhan, sukulkar, till, vbenes |
Target Milestone: | rc | Keywords: | Rebase, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | NetworkManager-1.40.0-1.el9 | Doc Type: | Enhancement |
Doc Text: |
.NetworkManager rebased to version 1.40
The `NetworkManager` packages have been upgraded to upstream version 1.40, which provides a number of enhancements and bug fixes over the previous version:
* The device state files in the `/run/NetworkManager/devices/` directory now have new sections, `[dhcp4]` and `[dhcp6]`, which contain the DHCP options of the current lease.
* NetworkManager supports setting an IPv6 Maximum Transmission Unit (MTU) in the `ipv6.mtu` property of connections.
* NetworkManager uses the `nm.debug` kernel command line option to enable debug logging.
* Carrier detection has been improved.
* NetworkManager now restarts the DHCP client for a connection if the MAC address changes on a device.
* Wifi hotspots now use a stable random channel number unless you select a specific channel.
* NetworkManager now disables the Wi-Fi Protected Access 3 (WPA3) transition mode if you set the `wifi.key-mgmt` property to `wpa-psk` and the network interface does not support Protected Management Frames (PMF). The transition mode caused problems in certain setups in this scenario. To explicitly enable the WPA3 transitioning mode, set `wifi.key-mgmt` to `sae`.
* NetworkManager now shortens an excessively long hostname received from a DHCP server to the first dot or to 64 characters.
* NetworkManager prefers the first static IPv6 address from the `ipv6.addresses` property and the order has been inverted to be consistent with how NetworkManager handles multiple IPv4 addresses in a connection profile.
For further information about notable changes, read the link:https://github.com/NetworkManager/NetworkManager/blob/nm-1-40/NEWS[upstream release notes].
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-15 10:49:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Thomas Haller
2022-04-21 09:21:02 UTC
*** Bug 2077409 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8265 |