Hi: (...)
> # ovs-ofctl dump-flows br0
> NXST_FLOW reply (xid=0x4):
> cookie=0x0, duration=490.292s, table=0, n_packets=8033106,
> n_bytes=840743327, idle_age=0,priority=0 actions=NORMAL
> # ovs-ofctl dump-flows br1
> NXST_FLOW reply (xid=0x4):
No flow for bridge br1 ??
> IP address:
> br0 -> 10.0.1.1
> tap0 -> 10.0.1.2
> br1 -> 10.0.0.1
> tap1 -> 10.0.0.2
I'm assuming that netmask is 255.0.0.0 (or 255.255.0.0).
> My ultimate goal is ping from tap0(10.0.1.2) to tap1(10.0.0.2), and my
> question is the following:
>
> 1. Do I really need to tag 100 on br0? If I omit tag=100 from br0, arp
> request/reply will not succeed somehow. The arp request is then propagated
> to br1 (I don't know why) which is totally useless.
AFAIK, for your goal it isn't necessary to set tag 100 to br0. Doing
so you should just 'capture' vlan 100 frames at br0 interface,
but others frames should be normally bridged.
I did a little experiment here, with a setup similarly with yours.
Using two guest hosts, one attached to tap0 and the other one to tap1.
Everything worked as expected, I could ping from one host to another.
Here goes some data:
$ sudo ovs-vsctl show
f622df30-ae47-447f-a264-e46ee49795e2
Bridge "br0"
Port "br0trunk"
trunks: [100]
Interface "br0trunk"
type: patch
options: {peer="br1trunk"}
Port "br0"
Interface "br0"
type: internal
Port "tap0"
tag: 100
Interface "tap0"
Bridge "br1"
Port "br1trunk"
trunks: [100]
Interface "br1trunk"
type: patch
options: {peer="br0trunk"}
Port "tap1"
tag: 100
Interface "tap1"
Port "br1"
Interface "br1"
type: internal
$ sudo ovs-ofctl dump-flows br0NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=2907.051s, table=0, n_packets=2997,
n_bytes=298734, idle_age=1, priority=0 actions=NORMAL
$ sudo ovs-ofctl dump-flows br1
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=2905.721s, table=0, n_packets=2965,
n_bytes=294622, idle_age=0, priority=0 actions=NORMAL
I'm using OVS from git repository with datapath kernel module:
openvswitch: Open vSwitch switching datapath 1.10.90, built Feb 16 2013 15:45:10
Attached to this email goes the ovsdb-server's conf.db I created.
regards
Lucas Brasilino
conf.db
Description: Binary data
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
