[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openvswitch-discuss
Subject:    [ovs-discuss] ovs-ofctl questions
From:       blp () nicira ! com (Ben Pfaff)
Date:       2013-01-31 15:31:44
Message-ID: 20130131153144.GA8192 () nicira ! com
[Download RAW message or body]

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:00:0a:01:00:05,dst˙:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip.1.0.5,tip.1.0.1,op=1,sha:00:0a:01:00:05,tha:00:00:00:00:00), \
> packets:65, bytes:2730, used:1.148s, actions:push_vlan  (vid ,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.


[prev in list] [next in list] [prev in thread] [next in thread]