FEATURE REQUEST: OpenVPN-SSTP-L2TP version 2-3-IKEV2 etc DCO (Data Channel Offloading)

RouterOS RouterOS beta
1

Hello,

Please MikroTik, If possible consider implementing DCO for OpenVPN-SSTP-L2TP version 2-3-IKEV2 etc. if it is not too difficult. This will significantly improve the performance of OpenVPN-SSTP-L2TP version 2-3-IKEV2 etc. (3-4 times or even more), reduce latency and CPU load, even when using low-power devices as access servers.

Please implement in RouterOS for routers and RouterOS for virtual servers (CHR).Implement on all CPU architectures.

I request MikroTik administrators and programmers OpenVPN-SSTP-L2TP version 2-3-IKEV2 etc. Add DCO (Data Channel Override)

Thanks
Amir Mahdavi Yousefi

2

Does SSTP,L2TP use DCO at all? Isn't it a OpenVPN thing?

3

Nein, niet.

4

I said if it is possible
I searched the internet and saw that it is for OpenVPN.
This feature should be added to be compatible with other (SSTP-L2TP version 2-3-IKEV2 etc).

Thanks
Amir Mahdavi Yousefi

5

DAnk für Ihre Antwort

EDIT:
I wonder what part of ROS work in user space, not in kernel?

6

Encryption, decryption, and VPN traffic go through the CPU.
And it puts pressure on the CPU, which is why I said add this feature if possible.

7

Don’t buy cheap hardware if you want ZUPER DUPER BLAZING ULTRA-FAST QUANTUM-ENCRYPTED MILITARY-GRADE NITRO VPN with NEGATIVE LATENCY and HYPER-TUNNEL TECHNOLOGY

8

Please explain me if you expect that decryption/encryption wouldn't be done by CPU just because it was moved from user space to kernel? What processes kernel code?
I assume that you suggest that switching back&forth user space/kernel is waste of time.

I think that ROS i mostly kernel thing. I could be wrong. Anyone knows?

9

I hardly doubt the whole openvpn daemon has been re-implemented in kernel space - that'd be a massive and very risky effort.

Same goes for other networking daemons.

What DCO brings to the table is data path in kernel space: all traffic is fully processed in kernel from reception on the NIC, until it gets delivered to the related interface.

A quick test to prove its potential benefit is to take a MikroTik board that also runs on Linux/OpenWrt and compare speed with ROS.