Is there a doc for the vlan_mode ? Actually I am pretty confused with the vlan_mode setting. In any case, I think what I want to accomplish is to make port br0, vnet0 to perform 'trunking' and port vlan100 to perform tagging for vlan 100. My benchmark is qemu. I got it working with qemu with either vlan_mode 'native-untagged' or 'native-tagged', while setting vlan_mode=access for vlan100. Setting br0 and vnet0 to vlan_mode=trunk will make the result worse. The same working open vswitch configuration is not working with virtualbox. I did some sniffing or tcpdump, I think it's looks like stucked at arp reply. That's why I posted it to virtualbox forum initially. From: Ben Pfaff <b...@nicira.com> To: Ming-Ching Tiew <mct...@yahoo.com> Cc: "discuss@openvswitch.org" <discuss@openvswitch.org> Sent: Thursday, March 5, 2015 12:36 AM Subject: Re: [ovs-discuss] Problem using virtualbox with open vswitch with VLAN Did you add a tag?
On Wed, Mar 04, 2015 at 06:14:39AM +0000, Ming-Ching Tiew wrote: > Please bear with me as I don't quite understand the significance of the > vlan_mode setting. > In any case, I changed the br0 port and vnet0 port to > vlan_mode=native-tagged, still guest 1 is not able to ping guest 2. The ping > result is the same as before. > > From: Ben Pfaff <b...@nicira.com> > To: Ming-Ching Tiew <mct...@yahoo.com> > Cc: "discuss@openvswitch.org" <discuss@openvswitch.org> > Sent: Wednesday, March 4, 2015 1:56 PM > Subject: Re: [ovs-discuss] Problem using virtualbox with open vswitch with >VLAN > > On Tue, Mar 03, 2015 at 09:55:26PM -0800, Ben Pfaff wrote: > > > > On Wed, Mar 04, 2015 at 01:45:44AM +0000, Ming-Ching Tiew wrote: > > > I posted this to virtualbox forum which I got no response and now I am > > > posting it here as it might be a openvswitch problem instead of > > > virtualbox :- > > > I have used virtualbox with open vswitch without any problem when I am > > > not using VLAN. > > > > > > However, when I am using VLAN tagging in one of the open vswitch port, I > > > cannot get it working. > > > > > > Here is the host ( debian 14.04 64 bit ) :- > > > > > > for i in 0 1 > > > do > > > ovs-vsctl add-br br$i > > > ip tuntap add mode tap vnet$i > > > ip link set vnet$i up > > > ovs-vsctl add-port br$i vnet$i > > > done > > > > > > ifconfig br0 192.168.2.2 up > > > ifconfig br1 192.168.3.1 up > > > > > > # add a port to switch br0 to have vlan tagging > > > ip tuntap add mode tap vlan100 > > > ip link set vlan100 up > > > ovs-vsctl add-port br0 vlan100 tag=100 > > > > > > # optional settings > > > # set other ports to trunk and untagged > > > ovs-vsctl set port vnet0 trunks=100 > > > ovs-vsctl set port vnet0 vlan_mode=native-untagged > > > ovs-vsctl set port br0 trunks=100 > > > ovs-vsctl set port br0 vlan_mode=native-untagged > > > > It does not make sense to specify native-untagged mode without > > specifying a tag, e.g. I guess you want to add tag=100 in each case. > > Also it looks like later you actually want packets going to port vnet0 > at least in the native VLAN to be tagged. That's native-tagged mode, > not native-untagged mode. > > >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
