[ovs-dev] [PATCH 0/6] Fix tunnel information destination port
Alin Serdean
aserdean at cloudbasesolutions.com
Tue Jan 10 16:48:28 UTC 2017
Deploying a simple environment using VXLAN encapsulation at the moment
does not work under Hyper-V. The tunnel information sent
by the userspace is not fully treated in the datapath.
To be more specific every packet that tries to be encapsulated via VXLAN tunnel
triggers the following line:
https://github.com/openvswitch/ovs/blob/75e2077e0c43224bcca92746b28b01a4936fc101/datapath-windows/ovsext/Flow.c#L1754
which is followed by a set action fail.
The actual attribute that triggers the above is: OVS_TUNNEL_KEY_ATTR_TP_DST.
This series adds support for that attribute and updates the current tunnel implementations.
Alin Serdean (6):
datapath-windows: Fix alignment in MapTunAttrToFlowPut
datapath-windows: Allow tunnel action to modify destination port
datapath-windows: Add support for OVS_TUNNEL_KEY_ATTR_TP_DST
datapath-windows: VXLAN Check for flow destination port
datapath-windows: STT Check for flow destination port
datapath-windows: GENEVE Check for flow destination port
datapath-windows/ovsext/Actions.c | 4 ++--
datapath-windows/ovsext/Flow.c | 10 +++++++++-
datapath-windows/ovsext/Geneve.c | 3 ++-
datapath-windows/ovsext/Stt.c | 3 ++-
datapath-windows/ovsext/Vxlan.c | 3 ++-
5 files changed, 17 insertions(+), 6 deletions(-)
--
2.10.2.windows.1
More information about the dev
mailing list