On Sat, 1 Sep 2018 03:16:34 -0400 Gabriel Filion <gabster@lelutin.ca> wrote: > > wooledg:~$ cat /lib/systemd/system/networking.service > > [...] > > [Service] > > Type=oneshot > > EnvironmentFile=-/etc/default/networking > > ExecStartPre=-/bin/sh -c '[ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle' > > ExecStart=/sbin/ifup -a --read-environment > > This seems to be problematic.. unfortunately if I understand correctly > "allow-hotplug" is meant to make it possible to have the network > interface be configured dynamically whenever it appears. So it might be > useful for network interface dongles ... but if I try to reason why > debian's installer configures interfaces as "allow-hotplug" by default, > I would guess that it might also be useful for laptops that have wifi > on/off physical switches to disable/enable the interface. > > I'm wondering why physical interfaces (previously known as ethN) would > require this instead of using "auto", though.. I've just tested changing "allow-hotplug enp0s25" to "auto enp0s25" as suggested by Greg as a workaround. Then I've rebooted the machine multiple times and I ended up seeing the problem again. So I believe that this workaround does not fix the issue after all. the bug lies somewhere else :\ is it possible that "udevadm settle" is the command that gets stuck sometimes?
Attachment:
signature.asc
Description: OpenPGP digital signature