Bug 1659063 - Missing static routes from custom table after NM initialization
Summary: Missing static routes from custom table after NM initialization
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.0
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: 8.0
Assignee: Thomas Haller
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-13 13:52 UTC by Thomas Haller
Modified: 2019-06-14 02:06 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.14.0-9.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1639274
Environment:
Last Closed: 2019-06-14 02:06:32 UTC
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Comment 2 Thomas Haller 2018-12-13 13:58:07 UTC
Notes for QA:

When NM now changes the MAC address, it first tries to do so without taking the interface down. That is preferred, because taking an interface down causes kernel to drop IPv4 routes and IPv6 addresses and routes. In particular, that is bad if the user added them externally (e.g. with a dispatcher scripts).

So, NM tries to avoid taking it down, except:

 - not for Wi-Fi devices (see bug 1656157)

 - if changing the MAC address fails, NM assumes it was because the driver didn't allow to change the MAC address while being up. In that case, NM takes the interface down, tries again to set the MAC address, and takes the interface up again.


Note You need to log in before you can comment on or make changes to this bug.