Package: bridge-utils Version: 1.7-1 Severity: normal Tags: ipv6 Dear Maintainer, when using the network/interfaces scripts to set up a bridge, they will automatically and unconditionally disable ipv6 not only on the ports added to the bridge, but also on the underlying physical device (if the port is a VLAN device). This is not always desirable (actually I wonder if it's ever desirable), e.g. in my setup I'm bridging a VLAN device on my physical NIC with veth devices attached to LXC containers, so the containers' traffic is always sent to a specific VLAN. However I still want to use the physical interface for the host's own traffic.
Thanks, -- Anton Khirnov -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'testing'), (500, 'stable'), (400, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-11-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages bridge-utils depends on: ii libc6 2.31-11 bridge-utils recommends no packages. Versions of packages bridge-utils suggests: ii ifupdown 0.8.36 -- no debconf information -- debsums errors found: debsums: changed file /lib/bridge-utils/bridge-utils.sh (from bridge-utils package) debsums: changed file /lib/bridge-utils/ifupdown.sh (from bridge-utils package) ^^ the local changes are just commenting out the lines disabling ipv6
