On Sat, Apr 5, 2014 at 3:45 AM, Claudia <dmcver...@gmail.com> wrote:
> Hi all:
>
> I establish a GRE tunnel between two openvswitch on two PC, and the
> configuration is as follow:
>
> PC-A(163.22.21.120)
> # ovs-vsctl show
> Bridge "ovs0"
> Controller "tcp:163.22.21.123:6633"
> Port "vnet0"
> Interface "vnet0"
> Port "gre0"
> Interface "gre0"
> type: gre
> options: {key="999", remote_ip="163.22.21.121"}
> Port "eth0"
> Interface "eth0"
> Port "ovs0"
> Interface "ovs0"
> type: internal
> ovs_version: "1.11.0"
>
> PC-B(163.22.21.121)
> # ovs-vsctl show
> Bridge "ovs0"
> Controller "tcp:163.22.21.123:6633"
> Port "gre0"
> Interface "gre0"
> type: gre
> options: {key="999", remote_ip="163.22.20.120"}
> Port "ovs0"
> Interface "ovs0"
> type: internal
> Port "tap0"
> Interface "tap0"
> Port "eth0"
> Interface "eth0"
> ovs_version: "1.11.0"
> Both PC-A and PC-B use the same OS(CentOS 6.4) and same Linux kernel
> (2.6.32-431.11.2.el6.x86_64).
>
> I write some app to make ovs0 on PC-A send the data from vnet0 to ovs0 on
> PC-B via GRE tunnel. I am sure that PC-B get the GRE tunnel packet by using
> "tcpdump -i eth0 proto gre" in PC-B. However, I don't know how to match the
> decapsulated packet then output to port tap0. ( I try to match if the
> in_port is gre0's port number or not. But the rule is always not be hit.)
>
> The following rule is the flow entry in PC-B
> # ovs-ofctl dump-flows ovs0
> NXST_FLOW reply (xid=0x4):
> cookie=0x0, duration=22.05s, table=0, n_packets=0, n_bytes=0, idle_age=22,
> priority=999,in_port=2 actions=output:3
> cookie=0x0, duration=22.05s, table=0, n_packets=1773, n_bytes=214020,
> idle_age=0, priority=999 actions=NORMAL
You need to specify different priorities for these rules. Since they
both match, the result is undefined.
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
