Patrick M. Hausen: > In that case a valid configuration would be: > > VLAN 1 on igb0: igb0.1 > VLAN 2 on igb0: igb0.2 > > VLAN 1 on igb1: igb1.1 > VLAN 2 on igb1: igb1.2 > > bridge1: igb0.1 igb1.1 > bridge2: igb0.2 igb2.2 > > All layer 3 configuration, all packet filtering, etc. on the bridge > interfaces. > No native frames on either igb0 or igb1. > > That's how it was supposed to work and did perfectly well. > > One bridge interface per VLAN - what's wrong with that?
your configuration is fine and nothing will change about that if you
want to continue configuring it this way.
the situation i'm talking about is when you have a vlan(4) configured on
an interface, and the underlying interface (not the vlan interface) is
also in a bridge, for example:
ifconfig vlan0 create vlan 101 vlandev ix0
ifconfig bridge0 create addm ix0
"ix0" has a vlan(4) configured on it and is also in a bridge: this is
the configuration i want to prohibit.
the text you quoted was not supposed to indicate that will be the *only*
way to configure vlans and bridges, only to explain the direction i'm
going in with recent changes to bridge. but bridge will always be able
to bridge any type of Ethernet interface, including vlan(4), if that's
how you want to use it.
signature.asc
Description: PGP signature
