From f3db8049b7f92548d1071b0b284a581b2226d1db Mon Sep 17 00:00:00 2001 From: Thomas Haller Date: Tue, 3 May 2022 12:26:44 +0200 Subject: [PATCH] NEWS: update Resync latest changes from nm-1-38 branch. --- NEWS | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/NEWS b/NEWS index 9db05c5b7f..b01faa063c 100644 --- a/NEWS +++ b/NEWS @@ -13,13 +13,6 @@ USE AT YOUR OWN RISK. NOT RECOMMENDED FOR PRODUCTION USE! * The nmcli command now supports --offline argument with "add" and "modify" commands, allowing operation on keyfile-formatted connection profiles without the service running (e.g. during system provisioning). -* Static IPv6 addresses from "ipv6.addresses" are now preferred over - addresses from DHCPv6, which are preferred over addresses from autoconf. - This affects IPv6 source address selection, if the rules from - RFC 6724, section 5 don't give a exhaustive match. -* Static IPv6 addresses from "ipv6.addresses" are now interpreted with - first address being preferred. Their order got inverted. This is now - consistent with IPv4. * The device state file /run/NetworkManager/devices/$ifindex now has new sections [dhcp4] and [dhcp6] containing the DHCP options for the current lease. @@ -30,8 +23,17 @@ Overview of changes since NetworkManager-1.36 ============================================= * Add support for route type "throw". +* Fix bug setting priority for IP addresses. +* Static IPv6 addresses from "ipv6.addresses" are now preferred over + addresses from DHCPv6, which are preferred over addresses from autoconf. + This affects IPv6 source address selection, if the rules from + RFC 6724, section 5 don't give a exhaustive match. +* Static IPv6 addresses from "ipv6.addresses" are now interpreted with + first address being preferred. Their order got inverted. This is now + consistent with IPv4. * Wi-Fi hotspots will use a (stable) random channel number unless one is chosen manually. +* Don't use unsupported SAE/WPA3 mode for AP mode. * NetworkManager will no longer advertise frequencies as supported when they're disallowed in configured regulatory domain. * Attempt to connect to WEP-encrypted Wi-Fi network will now fail