Hi Ben, Yes, it will be good to have these on 2.7 as well.
Thanks, Sairam -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ben Pfaff Sent: Thursday, February 2, 2017 10:53 AM To: Alin Serdean <[email protected]> Cc: [email protected] Subject: Re: [ovs-dev] [PATCH 0/6] Fix tunnel information destination port On Tue, Jan 10, 2017 at 04:48:28PM +0000, Alin Serdean wrote: > 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://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvs > witch_ovs_blob_75e2077e0c43224bcca92746b28b01a4936fc101_datapath-2Dwin > dows_ovsext_Flow.c-23L1754&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=Z6vowHU > OjP5ysP_g372c49Nqc1vEKqHKNBkR5Q5Z7uo&m=6Sjd7sTDI_6S1unUsi7L1N_smHiu0KY > gzgelATTDKC8&s=qhs6PeGOp6VJlBNJ3iskoP4odhoCQWMUoZINexxmDJA&e= > 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. Patch 1 was already on master. I've now applied patches 2 through 5 to master. Please let me know if you want these on branch-2.7 also. Thanks, Ben. _______________________________________________ dev mailing list [email protected] https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=Z6vowHUOjP5ysP_g372c49Nqc1vEKqHKNBkR5Q5Z7uo&m=6Sjd7sTDI_6S1unUsi7L1N_smHiu0KYgzgelATTDKC8&s=7klAtQ4aN6BXfMfvMe_rkcro6tK5viBHUqel951s9T4&e= _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
