Bug 1868982

Summary: backport route-related fixes from nm-1-26 to NetworkManager
Product: Red Hat Enterprise Linux 8 Reporter: Thomas Haller <thaller>
Component: NetworkManagerAssignee: Thomas Haller <thaller>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.3CC: acardace, atragler, bgalvani, lrintel, rkhan, sukulkar, thaller, till, vbenes
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.26.0-6.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 01:48:00 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 2020-08-14 20:40:56 UTC
nm-1-26 has two fixes that should be backported to rhel-8.3:

[1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/cf3cff4f12e78615c18fd829b1f32eac4f607c0b
[2] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/99b362c9443591b2b643aa09980f1a5dd42b1f6b



The problem that [1] fixes is the the following. On D-Bus we expose some IP routes. But for these routes, we don't export the "type" (presumably, they are all of the "unicast" type). Since 1.26, NetworkManager also supports "type local" routes.

The problem is that NM will now also export "type local" routes, but since their type cannot be seen, they look like normal routes. That is wrong.

Eventually we may want to export local routes too, but then we must properly mark their type.

Test: see the routes in `nmcli` output. Note that there are some routes there, that are actually the local types (compare with `ip route`). Patch [1] will remove these routes.


[2] is more subtle. We have a fuzzy understanding what a "default route" is, and in certain (non-clearly defined) situations we take special care of "default routes". Without [2], NetworkManager will also treat /0 routes of "type local" as default route. While all of this is not well defined, it still seems mostly wrong in this context. The fix is simple.

Comment 7 errata-xmlrpc 2020-11-04 01:48:00 UTC
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-2020:4499