Your message dated Tue, 15 Jan 2019 14:31:32 +0100
with message-id <[email protected]>
and subject line unsupported configuration
has caused the Debian Bug report #862657,
regarding bridge-utils: shutting down a bridge causes eth0 to shutdown even
while still in use for vlans
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
862657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862657
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bridge-utils
Version: 1.5-9
Severity: important
We have the following setup:
br0 connected to eth0.6 (vlan 6)
br1 connected to eth0.7 (vlan 7)
br2 connected to eth0
When shutting down br2 (ifdown br2), it takes down eth0, thereby also shutting
down the link for eth0.6 and eth0.7 and disconnecting the machine.
This seems to me like undesirable, eth0.6 and eth0.7 are still in use and
should stay up. Can it be changed that eth0 does not go down when it is still
in used in other places? If not, is there a way where I could shut down br2
without breaking the rest of the setup?
Thanks!
Sebastian
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages bridge-utils depends on:
ii libc6 2.19-18+deb8u6
bridge-utils recommends no packages.
Versions of packages bridge-utils suggests:
ii ifupdown 0.7.53.1
-- no debconf information
--- End Message ---
--- Begin Message ---
I haven't had more feedback on this and this configuration (binding eth0 and
its vlan subinterfaces) seems unsupported, I'm closing the bug.
Regards.
--
Manty/BestiaTester -> http://manty.net
--- End Message ---
