Package: ifupdown2 Version: 3.0.0-1 Severity: normal Dear Maintainer,
When I use ifupdown2 and have lxc containers running on the system (using VETH), I lose all connectivity to them when using ifreload -a. Their interfaces are DOWN. I expected it to not affect my containers' connectivity (as it is the case on Proxmox). To replicate, use ifupdown2 + lxc containers (using VETH). Then enter ifreload -a on the console. Their interfaces should not go down in this way. -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-17-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8), LANGUAGE=en_US.utf8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ifupdown2 depends on: ii iproute2 5.10.0-4 ii python3 3.9.2-3 ifupdown2 recommends no packages. Versions of packages ifupdown2 suggests: ii bridge-utils 1.7-1 ii ethtool 1:5.9-1 ii isc-dhcp-client 4.4.1-2.3 pn python3-gvgen <none> pn python3-mako <none> -- no debconf information
