[ovs-discuss] ovs-ofctl questions

[Ben Pfaff]

If you just give the two machines the same VLAN tag then you don't have
to add any flows.  That would be the usual solution.

On Fri, Feb 01, 2013 at 09:43:47AM +0800, ?????? wrote:
> hi Ben:
> How should I add a flow to make two virtual machines Ping pass, please help.
> Thank you!
> 
> 
> 
> 
> ??????
> 
> From: Ben Pfaff
> Date: 2013-01-31 23:31
> To: ??????
> CC: discuss
> Subject: Re: [ovs-discuss] ovs-ofctl questions
> On Thu, Jan 31, 2013 at 04:28:13PM +0800, ?????? wrote:
> > hi all:
> >     I have two  virtual machines ,they have a different vlan tag,asfollws
> > 
> > [root at node50 ~]# ovs-vsctl show
> > 98dd8985-540b-4838-a321-11006fa96694
> >     Bridge "virbr0"
> >         Port "virbr0-nic"
> >             Interface "virbr0-nic"
> >         Port "virbr0"
> >             Interface "virbr0"
> >                 type: internal
> >     Bridge "br0"
> >         Port "br0"
> >             Interface "br0"
> >                 type: internal
> >         Port "vnet1"
> >             tag: 20
> >             Interface "vnet1"
> >         Port "eth0"
> >             Interface "eth0"
> >         Port "vnet0"
> >             tag: 10
> >             Interface "vnet0"
> >     ovs_version: "1.7.1" 
> >    
> >    I used the ovs-ofctl to modify the vnet0 vlan tag, as follows 
> > 
> >    [root at node50 ~]# ovs-ofctl add-flow br0 idle_timeout=0,in_port=2,actions=mod_vlan_vid:20,output:3("3" is vnet1 port)
> >    
> >    Then I used ovs-dpcta View package,
> >    in_port(2),eth(src=02:00:0a:01:00:05,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=10.1.0.5,tip=10.1.0.1,op=1,sha=02:00:0a:01:00:05,tha=00:00:00:00:00:00), packets:65, bytes:2730, used:1.148s, actions:push_vlan  (vid=20,pcp=0),3
> >    
> >     the vlan id has changed to 20 ,but two virtual machines to each other or the ping fails.
> 
> The flow you added doesn't make much sense.  You defined vnet1 as an
> access port but your flow treats it as a trunk port by sending it a
> packet with a VLAN tag.
> ---------------------------------------------------------------------------------------------------
> Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) 
> is intended only for the use of the intended recipient and may be confidential and/or privileged of 
> Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is 
> not the intended recipient, unauthorized use, forwarding, printing,  storing, disclosure or copying 
> is strictly prohibited, and may be unlawful.If you have received this communication in error,please 
> immediately notify the sender by return e-mail, and delete the original message and all copies from 
> your system. Thank you. 
> ---------------------------------------------------------------------------------------------------