Hi! In the mean time, I moved all of our servers to Proxmox, which has a filter built-in to avoid affecting veth interfaces. Also, I fixed it by adding this to my bridge's config: bridge-ports-condone-regex ^(tap|veth|fwpr)
Personally, I think that ifupdown2 should just have this condone by default, but that's me. All the best, Karl On Wednesday, October 22, 2025 14:31 CEST, Fabian Grünbichler <[email protected]> wrote: On September 23, 2022 1:27 pm, Karl Heinz Grube wrote: > 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. hi! could you please provide the output of - ip -a - ip -l the contents of your /etc/network/interfaces (.d/*) as well as the output of - ifreload -av feel free to censor sensitive information like MAC or IP addresses, but please do so consistently. thanks! -- Dr. Karl Grube, System Engineer EOX IT Services GmbH - https://eox.at1090 Wien, Thurngasse 8/4, Austria+43 660 2957764 - [email protected]
