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.
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
