> It happens because udev rules are applied too later, when interfaces have been up and configured.
we can disable udev rules processing by
# udevadm control --stop-exec-queue
and then enable it back with
# udevadm control --start-exec-queue
however, this seems to be too fragile and could have additional side effects as well.
> It happens because udev rules are applied too later, when interfaces have been up and configured.
we can disable udev rules processing by
# udevadm control --stop-exec-queue
and then enable it back with
# udevadm control --start-exec-queue
however, this seems to be too fragile and could have additional side effects as well.