Bug 1399799 - RFE: ovs should refuse multiple tunnels on the same port
Summary: RFE: ovs should refuse multiple tunnels on the same port
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openvswitch
Version: 7.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Eelco Chaudron
QA Contact: Rick Alongi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-29 18:44 UTC by Thadeu Lima de Souza Cascardo
Modified: 2018-09-07 18:12 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-07 18:12:59 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Thadeu Lima de Souza Cascardo 2016-11-29 18:44:02 UTC
If one configures multiple VXLAN tunnels on the same port, with different flags (like GBP), OVS won't be able to handle that. It should refuse such configurations.

See RFC/patch and discussion upstream.

https://mail.openvswitch.org/pipermail/ovs-dev/2016-June/315570.html

Comment 4 Eelco Chaudron 2017-06-09 09:28:23 UTC
I have submitted a new patch, but I think this patch was not needed to begin with. I've asked upstream to also comment on this. Patch is here:

https://mail.openvswitch.org/pipermail/ovs-dev/2017-June/333750.html

Comment 5 Eelco Chaudron 2017-07-25 12:35:10 UTC
Need to do some more testing to see what Linux support in the datapath and re-send (or ack) patch.

Comment 6 Eelco Chaudron 2018-02-09 14:45:26 UTC
Submitted v2 patch after confirming current implementation does not support concomitant tunnels.

https://mail.openvswitch.org/pipermail/ovs-dev/2018-February/344326.html

Comment 7 Eelco Chaudron 2018-06-01 17:05:41 UTC
Sent out a v3 patch:

https://mail.openvswitch.org/pipermail/ovs-dev/2018-June/347807.html

Comment 8 Eelco Chaudron 2018-09-03 14:37:33 UTC
Sent out a v4 of the patch:

https://mail.openvswitch.org/pipermail/ovs-dev/2018-September/351805.html


Note You need to log in before you can comment on or make changes to this bug.