Hi, This is a followup for Debian bug <http://bugs.debian.org/352991>.
On Wed, Feb 15, 2006, [EMAIL PROTECTED] wrote: > vlan does not integrate well with bridged interfaces/bridge utils. Problems > observed: > 1. br0.100 and br0.200 is not brought up until /etc/networking/*.d/vlan > script cases are extended I'm not sure of what br0.100 is supposed to mean. br0 is not a 100% compatible ethernet device. (See below.) > 2. /etc/init.d/networking restart does not shut interfaces in proper order. I > guess it may not be issue with vlan but maybe some higher level utility? restart should bring them down in the reverse order they were brought up I suppose. > auto br0 > iface br0 inet manual > bridge_ports eth0 eth1 > > auto br0.100 > iface br0.100 inet static > address 192.168.253.5 So, does this mean that you would like to do 802.1Q on eth0 and eth1, bridge the 802.1Q traffic, and have a per vlan interface on your host that sees normal Ethernet traffic? This seems a bit weird to me. What I could imagine is: - eth0 and eth1 have 802.1Q traffic - you have eth0.100, eth0.200, eth1.100, eth1.200 with normal Ethernet traffic - you bridge eth0.100 with eth1.100 in br0, and eth0.200 and eth1.200 in br1 This achieves the same result, but with a per VLAN bridge. Is anything making you prefer bridging of 802.1Q? Didn't you have any trouble with your setup? Bye, -- Loïc Minier <[EMAIL PROTECTED]>
