Opened 14 months ago

Closed 14 months ago

Last modified 14 months ago

#13804 closed enhancement (fixed)

NetworkManager-1.26.0

Reported by: Bruce Dubbs Owned by: Douglas R. Reno
Priority: normal Milestone: 10.0
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

New minor version.

Change History (5)

comment:1 by Douglas R. Reno, 14 months ago

Owner: changed from blfs-book to Douglas R. Reno
Status: newassigned

comment:2 by Douglas R. Reno, 14 months ago

Note that the security vulnerability described here was fixed in the last 1.24.x release that we upgraded to as well.

=============================================
NetworkManager-1.26
Overview of changes since NetworkManager-1.24
=============================================

* Add a new build option 'firewalld-zone'; when enabled,
  NetworkManager installs a firewalld zone for connection sharing and
  puts interfaces using IPv4 or IPv6 shared mode in this zone during
  activation. The option is enabled by default.
  Note that NetworkManager still calls to iptables to enable
  masquerading and open needed ports for DHCP and DNS. The new option
  is useful on systems using firewalld with the nftables backend,
  where the iptables rules would not be sufficient.
* Extend the syntax for 'match' setting properties with '|', '&', '!'
  and '\\'.
* Add MUD URL property for connection profiles (RFC 8520) and set it
  for DHCP and DHCPv6 requests.
* Expose raw LLDP message on D-Bus and the MUD usage description URL.
* ifcfg-rh: handle "802-1x.{,phase2-}ca-path". Otherwise setting this
  property silently fails and a profile might accidentally not perform
  any authentication (CVE-2020-10754).
* ifcfg-rh: handle 802-1x.pin properties.
* ethernet: reset original autonegotiation/speed/duplex settings when
  deactivating device.
* Support ethtool coalesce and ring options.
* Allow team connections to work without D-Bus (e.g. in the initrd).
* Wi-Fi profiles now also autoconnect if all previous activation attempts
  failed. This means, an initial failure to autoconnect to the network will
  no longer block the automatism. A side effect is that existing Wi-Fi profiles
  which previously were blocked may now start to autoconnect.
* NetworkManager now supports "local" type routes beside "unicast".
* Introduce new manual pages nm-settings-dbus and nm-settings-nmcli.
* Mark externally managed devices and profiles on D-Bus.
* Highlight externally managed devices in nmcli.
* Add support for a number of bridge options.
* Add match for device path, driver and kernel command line for connection
  profiles.
* Fix support for OVS patch interfaces.
* Support more tc qdiscs: tbf and sfq.
* Add new provider in nm-cloud-setup for Google Cloud Platform which
  automatically detects and configures the host to receive traffic
  from internal load balancers.

comment:3 by Douglas R. Reno, 14 months ago

Resolution: fixed
Status: assignedclosed

Fixed at r23391

comment:4 by Bruce Dubbs, 14 months ago

Milestone: 9.210,0

Milestone renamed

comment:5 by Bruce Dubbs, 14 months ago

Milestone: 10,010.0

Milestone renamed

Note: See TracTickets for help on using tickets.