You can register yourself in https://www.opennetworking.org/ then you can search any document.
From: Wieger IJntema [mailto:[email protected]] Sent: Wednesday, July 5, 2017 10:41 PM To: Yang, Yi Y <[email protected]>; [email protected] Subject: Re: [ovs-dev] GTP support to OVS upstream Dear Yi, I'm not fully updated on the current OpenFlow 1.6 specification. I have now created a workaround with two bridge interfaces on one machine to forward normal traffic and only inspect GTP traffic. But indeed this requires full decapsulation of the packet before we have any knowledge of the packet inside. (IP and tun_id) I have to look deeper in the GTP code to be sure if we should proceed the way you describe. But i have looked in the PTAP and the generic encap & decap solutions described here: https://www.mail-archive.com/[email protected]/msg71808.html and i think that is a solid basis to continue on. i'm new to the Openvswitch development is there a way i can view: EXT-382 Generic tunnel Encap and Decap issue? regards, Wieger IJntema On Wed, Jul 5, 2017 at 12:54 PM, Yang, Yi Y <[email protected]<mailto:[email protected]>> wrote: I remember OpenFlow 1.6 spec (not finalized) proposes to use OpenFlow actions to do GTP-u encapsulation and decapsulation, current OvS tunnel implementation can't support the third kind of use case (don't encap & decap, just parse, match and forward), MEC (ETSI Molibe/Multi-access Edge Computing) the third kind of use case. I'm wondering if it is feasible to implement a generic UDP tunnel in OvS, let Openflow do encap /decap/parse&match, now ovs master has fully supported L3 tunnel port and PTAP(Packet type aware pipeline), we have posted out generic encap & decap actions implementation, once ovs officially merges them, ovs can support generic encap & decap action, we can base on them to implement GTP-u encap & decap, then it will be better if we can implement a generic UDP tunnel, ovs can add UDP tunnel ports with different UDP port to handle different tunnel protocol, I think this will be the best way to handle the aforementioned three kinds of use cases. -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Wieger IJntema Sent: Wednesday, July 5, 2017 5:37 PM To: [email protected]<mailto:[email protected]> Subject: [ovs-dev] GTP support to OVS upstream Dear Developers, I would like to start a discussion to actually get native GTP tunneling support in Openvswitch keeping it still compatible with the current OpenFlow standard. https://en.wikipedia.org/wiki/GPRS_Tunnelling_Protocol I the past there has been a patch for OVS to actually have GTP support. https://www.mail-archive.com/[email protected]/msg56446.html, Feb 2016?, Niti Rohilla, OVS 2.5.0 Main concern was that there was no Linux upstream GTP support. This work is updated to work with version OVS 2.6.1 https://github.com/ashishkurian/ovs, Dec 2016, Ashish Kurian, OVS 2.6.1 I have tested it extensively if all nodes use the samen OVS version with GTP support it works good! It is just working like Lisp or GRE tunneling and you can set the key with the set "tunnel_id" command from openflow. I have used RYU as a controller to control multiple OVS switches with GTP tunneling. In mobile networks research there is a lot interest to get GTP support in OVS. Especially in development towards 5G mobile network, where Openflow is considered a protocol to be used there as switch-controller protocol. I'm currently testing this in "pre 5G" Core solution where GTP encapsulation is done by OVS. >From OSMOCOM.org there is now an GTP-U (GTP userplane) Linux upstream >implementation and it think we can use it together with the Openvswitch GTP >patch to get native GTP-U support in OVS. https://osmocom.org/projects/linux-kernel-gtp-u/wiki, Since linux kernel v4.7.0 https://www.kernel.org/doc/Documentation/networking/gtp.txt http://elixir.free-electrons.com/linux/v4.8.9/source/drivers/net/gtp.c I would like to start working on this, if you guys have suggestions or reservations please let me know. Regards, Wieger IJntema TNO _______________________________________________ dev mailing list [email protected]<mailto:[email protected]> https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
