Comment 60 for bug 2036358

I'm curious if this bug is still being investigated. RPI4 with wlan0, eth0 and eth1 (USB3 using r8152 driver) definitely manifests this bug. I need to wait ~30 minutes before either wlan0 or eth0 becomes available in order to restart systemd-networkd to activate eth1 and then ip link set up eth1. At that point the network appears stable until next reboot.

IDX LINK TYPE OPERATIONAL SETUP
  1 lo loopback carrier unmanaged
  2 eth0 ether routable configured
  4 wlan0 wlan routable unmanaged
  5 tun0 none routable unmanaged
  6 docker0 bridge routable unmanaged
  8 vethd334874 ether degraded unmanaged
  9 eth1 ether routable configured
 14 veth1a9ad92 ether degraded unmanaged
 16 vethe09f689 ether degraded unmanaged
 18 veth592971d ether degraded unmanaged
 19 macvlan-shim ether routable unmanaged
 21 vethafb615d ether degraded unmanaged

I hesitate using the word arbitrary but given how RPI4 utilizes both networkmanager and networkd it appears arbitrary to state that only networkmanager should be used in a desktop installation - at least I cannot find any documentation that supports not using both simultaneously. That said, I have been running this configuration for at least 2 years without issue *until* systemd was updated.

I'm a new Ubuntu-One user and this is my first post after waiting patiently for post #52 & #58 to get responses from anyone - so please forgive (and forget :). Constructive criticism humbly accepted.