[ovs-git] [openvswitch/ovs] dc0bd1: userspace: Enable non-bridge port as tunnel endpoint.

yifsun noreply at github.com
Wed Sep 25 22:24:35 UTC 2019


  Branch: refs/heads/master
  Home:   https://github.com/openvswitch/ovs
  Commit: dc0bd12f5b0444e34bf56fbbed556c0f1201c4f2
      https://github.com/openvswitch/ovs/commit/dc0bd12f5b0444e34bf56fbbed556c0f1201c4f2
  Author: Yifeng Sun <pkusunyifeng at gmail.com>
  Date:   2019-09-25 (Wed, 25 Sep 2019)

  Changed paths:
    M ofproto/ofproto-dpif-xlate.c
    M tests/packet-type-aware.at
    M tests/system-layer3-tunnels.at

  Log Message:
  -----------
  userspace: Enable non-bridge port as tunnel endpoint.

For userspace datapath, currently only the bridge itself, the LOCAL port,
can be the tunnel endpoint to encap/decap tunnel packets.  This patch
enables non-bridge port as tunnel endpoint.  One use case is for users to
create a bridge and a vtep port as tap, and configure underlay IP at vtep
port as the tunnel endpoint.

This patch causes failure for test "ptap - L3 over patch port". This is
because this test is already using non-bridge port gre1 as tunnel endpoint.
In this test, a flow is added to redirect tunnel packets to gre1 port,
as shown below:
  ovs-ofctl add-flow br1 in_port=p1,actions=output=gre1

It later generates a datapath flow which matches an extra eth field:
  - recirc_id(0),...,eth_type(0x0800),...
  + recirc_id(0),...,eth(dst=1e:2c:e9:2a:66:9e),eth_type(0x0800),...

With this patch, this flow need only a NORMAL action.

Signed-off-by: William Tu <u9012063 at gmail.com>
Co-authored-by: William Tu <u9012063 at gmail.com>
Signed-off-by: Yifeng Sun <pkusunyifeng at gmail.com>
Signed-off-by: Ben Pfaff <blp at ovn.org>




More information about the git mailing list