fh29 Hello, When using v3.2.3 on Windows 10, only a TAP v9 adapter is created. If I use an .ovpn config file with the option "windows-driver wintun" it seems to be ignored because no Wintun adapter is created and OpenVPN Connect continues to use the TAP v9 adapter. I remember a few months ago choosing during the installation between the two adapters/drivers but the option is not present anymore during the installation of v3.2.3. Is OpenVPN Connect still compatible with Wintun? Did it drop support for it?
openvpn_inc Hello fh29, We did a beta with wintun support, but have since gone back to TAP adapter. The advantage was the ability to get higher speeds on Windows. We have however ended this beta since OpenVPN Connect v3.2.3. A new project called OpenVPN DCO aims to improve speeds on Linux and Windows platforms. This is currently under development and in the community. Once mature we will offer an option to use that instead. It offers even better speeds. Kind regards, Johan
fh29 Hello, Thank you for the confirmation and additional info! Would it be possible to also answer my other (more important) issue? https://forums.openvpn.net/viewtopic.php?f=37&t=32325
Meserias Could you please explain how to use OpenVPN DCO ? What exact we should write in server and client side in order to use DCO ?
