Changes between Version 10 and Version 11 of DataChannelOffload

Timestamp:

01/16/22 21:32:26 (3 years ago)

Author:

Antonio Quartulli

Comment:

--

DataChannelOffload

@@ -23 +23 @@
 === Introducing DCO
 To overcome the limitations described in the section above we have developed ''ovpn-dco'', a Linux kernel module designed to work back-to-back with the OpenVPN userspace software.
-When a VPN connection is established, being it on a client, on a server or on a p2p instance, the userspace process will first perform the usual handshake and will then pass the data channel parameters to ovpn-dco, so that it can take over from there. At this point, data packets are all handled in kernelspace and are never sent up to the userspace process.
+When a VPN connection is established, being it on a client, on a server or on a p2p instance, the userspace process will first perform the usual handshake and will then pass the data channel parameters to ovpn-dco using its ''NetLink'' interface, so that it can take over from there. At this point, data packets are all handled in kernelspace and are never sent up to the userspace process.
 
 The picture below helps to visualize the difference with to the basic scenario shown above:
 
-{image here}
+[[Image(dco.png)]]
 
-Context switch is therefore reduced to the minimum and packet processing can take advantage of the kernel concurrency model.
-The two main OpenVPN functions, crypto and routing, are implemented using the kernel provided API.
+Context switches are therefore reduced to the minimum and packet processing can take advantage of the kernel concurrency model.
+The two main OpenVPN functions, crypto and routing, are now implemented in kernel using the provided API.
 For what concerns routing, the system routing table is directly used to understand if packets have to be re-routed directly to another peer (i.e. client-to-client mode), without the need to ask the userspace process at all.