[ovs-discuss] OVS layer3 GRE support

Hexin Wang hexin.wang at nutanix.com
Tue Apr 25 16:43:11 UTC 2017


Thanks Ben/Zoltan,

I will try out the patch and report back.

Thanks.

Hexin




On 4/25/17, 9:40 AM, "Zoltán Balogh" <zoltan.balogh at ericsson.com> wrote:

>Hi,
>
>I sent a new version of the patch set to the dev list:
>https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/331424.html
>
>Best regards,
>Zoltan
>
>> -----Original Message-----
>> From: ovs-discuss-bounces at openvswitch.org [mailto:ovs-discuss-bounces at openvswitch.org] On Behalf Of Ben Pfaff
>> Sent: Tuesday, April 25, 2017 5:38 AM
>> To: Hexin Wang <hexin.wang at nutanix.com>
>> Cc: simon.horman at netronome.com; ovs-discuss at openvswitch.org
>> Subject: Re: [ovs-discuss] OVS layer3 GRE support
>> 
>> Can you test or examine the recent patches to see if they avoid the
>> problem you mention?  It probably won't be obvious as a problem during
>> review.
>> 
>> On Tue, Apr 25, 2017 at 01:46:41AM +0000, Hexin Wang wrote:
>> > Thanks. Good to know that this is being merged back to OVS mainline.
>> >
>> > The old way of Layer3 GRE implementation via “base_layer” seems to have an issue with ct_state_nat feature.
>> > Specifically if pop_mpls happens before ct(nat,), pop_mpls recirculation would cause both flow->base_layer and
>> base_flow->base_layer to be LAYER_3. The recirculation triggered by ct(nat,) would fail if one of the commit actions
>> is to set layer2 header.
>> >
>> > Regards,
>> >
>> > Hexin
>> >
>> >
>> > On 4/24/17, 5:29 PM, "Yang, Yi Y" <yi.y.yang at intel.com> wrote:
>> >
>> > >The userspace L3 patch set Zoltan posted has included L3 support for GRE, here it is.
>> > >
>> > >https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/330490.html
>> > >
>> > >
>> > >-----Original Message-----
>> > >From: ovs-discuss-bounces at openvswitch.org [mailto:ovs-discuss-bounces at openvswitch.org] On Behalf Of Hexin Wang
>> > >Sent: Tuesday, April 25, 2017 2:42 AM
>> > >To: Ben Pfaff <blp at ovn.org>
>> > >Cc: simon.horman at netronome.com; ovs-discuss at openvswitch.org
>> > >Subject: Re: [ovs-discuss] OVS layer3 GRE support
>> > >
>> > >Right. I was specifically referring to the OVS layer3 tunnel support originated by Lorand Jakab and Simon Horman.
>> > >The changes made in kernel data path is merged back to Linux mainline by Jiri Benc. But the user space OVS
>> changes are missing in ovs main tree.
>> > >
>> > >Thanks.
>> > >
>> > >Hexin
>> > >
>> > >
>> > >
>> > >
>> > >On 4/24/17, 11:37 AM, "Ben Pfaff" <blp at ovn.org> wrote:
>> > >
>> > >>On Mon, Apr 24, 2017 at 06:25:07PM +0000, Hexin Wang wrote:
>> > >>> I got a question on OVS layer3 GRE tunnel support. The OVS kernel
>> > >>> piece that supports layer 3 GRE is merged into linux upstream since
>> > >>> 4.10 RC6. Do we need any extra user land OVS merge for it to work
>> > >>> end-to-end? I am referring to the “options:layer3=true” ovs-vsctl
>> > >>> interface changes. Essentially, how is “push_mpls” action triggering
>> > >>> the pop_eth action in kernel data path?
>> > >>
>> > >>This is not a subject I know well.  That said, it looks like OVS
>> > >>userspace doesn't currently support layer-3 GRE tunnels in an
>> > >>appropriate way.  I mainly base this on the code in
>> > >>netdev_vport_is_layer3(), which considers only LISP ports to be layer-3
>> > >>ports.
>> > >_______________________________________________
>> > >discuss mailing list
>> > >discuss at openvswitch.org
>> > >https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>> _______________________________________________
>> discuss mailing list
>> discuss at openvswitch.org
>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss


More information about the discuss mailing list