Jonas Meurer
2020-09-23 11:40:02 UTC
Package: ifupdown
Version: 0.8.35
Followup-For: Bug #959985
Control: severity -1 important
Hello,
I hit the same bug on a freshly installed Debian Buster system. It's a server
system with two NICs (eno1 + eno2) but only eno1 has a link. My interface config
is to have a bridge br0 started with eno1 as only bridge port.
Additionally, eno1 is started with an IP during initramfs in order to allow
remote LUKS unlocking by setting the `ip` kernel boot parameter. Maybe that's
related.
In my case, the failing `ifupdown-pre.service` results in the interface `br0`
not being brought up at all, leading to no network after boot.
The best workaround I found was to mask `ifupdown-pre.service`:
# systemctl mask ifupdown-pre.service
Afterwards, the system boots up without delay and interface `br0` is brought up
at boot.
Cheers
jonas
-- Package-specific info:
--- /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
--- /etc/network/interfaces.d/*:
# WAN bridge
auto br0
iface br0 inet static
bridge_ports eno1
# disable spanning tree protocol
bridge_stp off
bridge_fd 0
bridge_maxwait 0
address 172.16.42.10/24
gateway 172.16.42.1
--- up and down scripts installed:
/etc/network/if-down.d:
total 0
/etc/network/if-post-down.d:
total 0
lrwxrwxrwx 1 root root 29 Jan 28 2019 bridge -> /lib/bridge-utils/ifupdown.sh
/etc/network/if-pre-up.d:
total 0
lrwxrwxrwx 1 root root 29 Jan 28 2019 bridge -> /lib/bridge-utils/ifupdown.sh
/etc/network/if-up.d:
total 0
Version: 0.8.35
Followup-For: Bug #959985
Control: severity -1 important
Hello,
I hit the same bug on a freshly installed Debian Buster system. It's a server
system with two NICs (eno1 + eno2) but only eno1 has a link. My interface config
is to have a bridge br0 started with eno1 as only bridge port.
Additionally, eno1 is started with an IP during initramfs in order to allow
remote LUKS unlocking by setting the `ip` kernel boot parameter. Maybe that's
related.
In my case, the failing `ifupdown-pre.service` results in the interface `br0`
not being brought up at all, leading to no network after boot.
The best workaround I found was to mask `ifupdown-pre.service`:
# systemctl mask ifupdown-pre.service
Afterwards, the system boots up without delay and interface `br0` is brought up
at boot.
Cheers
jonas
-- Package-specific info:
--- /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
--- /etc/network/interfaces.d/*:
# WAN bridge
auto br0
iface br0 inet static
bridge_ports eno1
# disable spanning tree protocol
bridge_stp off
bridge_fd 0
bridge_maxwait 0
address 172.16.42.10/24
gateway 172.16.42.1
--- up and down scripts installed:
/etc/network/if-down.d:
total 0
/etc/network/if-post-down.d:
total 0
lrwxrwxrwx 1 root root 29 Jan 28 2019 bridge -> /lib/bridge-utils/ifupdown.sh
/etc/network/if-pre-up.d:
total 0
lrwxrwxrwx 1 root root 29 Jan 28 2019 bridge -> /lib/bridge-utils/ifupdown.sh
/etc/network/if-up.d:
total 0