On Sun, Dec 10, 2023 at 01:45:36AM -0000, Roger Nelson wrote:
> 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.
This bug report is about a change in behavior of the systemd wait-online
target at boot. "Need to wait 30 minutes before network device becomes
available" sounds unrelated. You should file a separate bug report for your
issue.
On Sun, Dec 10, 2023 at 01:45:36AM -0000, Roger Nelson wrote:
> 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.
This bug report is about a change in behavior of the systemd wait-online
target at boot. "Need to wait 30 minutes before network device becomes
available" sounds unrelated. You should file a separate bug report for your
issue.