[ovs-discuss] VXLAN port is broken on Windows

Alin Serdean aserdean at cloudbasesolutions.com
Tue Jan 10 16:54:11 UTC 2017


Further debugging shows that we were not treating another attribute(under Windows) which was causing the failures (OVS_TUNNEL_KEY_ATTR_TP_DST).

Please disregard the former question.

Thanks,
Alin.

From: ovs-discuss-bounces at openvswitch.org [mailto:ovs-discuss-bounces at openvswitch.org] On Behalf Of Alin Serdean
Sent: Friday, December 16, 2016 6:28 AM
To: ovs-discuss at openvswitch.org
Subject: [ovs-discuss] VXLAN port is broken on Windows

Hi,

I was testing on master and our Windows VXLAN implementation is broken.

The root cause is: userspace sends out OVS_TUNNEL_KEY_ATTR_VXLAN_OPTS

We could implement that functionality, but I was normal behavior when I have the following setup:
3c7cfa22-109c-4f6e-9652-d20a40527167
    Bridge br-tun
        Port br-tun
            Interface br-tun
                type: internal
        Port "vm1"
            Interface "vm1"
                type: internal
        Port vxlan
            Interface vxlan
                type: vxlan
                options: {in_key=flow, out_key=flow, remote_ip="13.13.13.1"}
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth2"
            Interface "eth2"
Ovs-ofctl dump-flows br-tun
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=3558.899s, table=0, n_packets=15875, n_bytes=1196584, idle_age=0, priority=0 actions=NORMAL

Thanks,
Alin.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20170110/62deaabb/attachment.html>


More information about the discuss mailing list