See, I knew this would be the group to ask. I missed that native-tagged/native-untagged was even an option. I set my eth1 port to native-tagged and voilĂ ! We have a running switch. This thing is pretty awesome. Thanks!
On Wed, Oct 2, 2013 at 7:12 PM, Ben Pfaff <b...@nicira.com> wrote: > On Wed, Oct 02, 2013 at 04:11:10PM -0400, Maxwell Bottiger wrote: > > I'm working off the the tutorial in the open vswitch VLANS cookbook. > I've > > followed the directions as best I could, but I still don't have things > > quite working correctly. To start with, here is my configuration: > > > > d70e42a8-1b7e-433d-a2c2-921e3c720e8e > > Bridge "bridge0" > > Port "tap1" > > tag: 2 > > Interface "tap1" > > Port "eth1" > > tag: 666 > > trunks: [2, 6] > > Interface "eth1" > > Port "tap0" > > tag: 6 > > Interface "tap0" > > Port "bridge0" > > Interface "bridge0" > > type: internal > > ovs_version: "1.4.3" > > > > > > I have eth1 of my workstation connected to the trunked port on one of my > > switches. The trunk VLAN is 666 on this setup. I have two tap > interfaces > > defined, one should be on VLAN 6, the other on VLAN 2. The desired > outcome > > is to have a virtual machine on tap0 connect straight through to VLAN6, > and > > a vm on tap1 connect directly through to the other resources on VLAN2. > I'm > > not sure if having a trunk with an odd PVID is throwing me off, or if > > there's something more I need to set. I looked at eth1 with wireshark, > and > > I can see traffic from all the other VLANs, so I'm pretty sure that > > connection is solid. I saw in other emails in the archive that people > > often wanted to see the ovs-ofctl output, so I'll include that too. > > Did you actually configure eth1 as native-tagged or native-untagged? > "ovs-vsctl show" doesn't display that, so I can't tell. >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss