Investigate whether internal network adapters consistently use their previously spoofed MAC address after resuming from suspend
On resume, apparently internal network adapters are not seen as “added”
by the kernel, so no udev event is triggered, so we don’t spoof their
MAC address again.
So it seems we’re implicitly relying on the assumption that all internal
network adapters and their firmware will remember and use their
previously spoofed MAC after resuming from suspend.
Is this actually true?
Note that if we let NetworkManager handle the whole MAC spoofing dance itself (#11293), we would not have to wonder.
Related issues
Original created by @intrigeri on 17128 (Redmine)