Existing Wintun adapters are removed ; Wintun incompatibility with openvpn
Establishing a connection using OpenConnect seems to remove all existing Wintun network adapters. In particular, this includes the ones created by OpenVPN (Community Version 2.6.8). How do I prevent this from happening?
Steps to reproduce:
- Install OpenVPN & OpenConnect
- Ensure that there is at least one Wintun network adapter, otherwise create one using the utility provided by OpenVPN
- Use OpenConnect to establish a VPN connection
- All Wintun adapters are removed
This seems to be the relevant part of the log:
Got CONNECT response: HTTP/1.1 200 OK
CSTP connected. DPD 30, Keepalive 30
Established DTLS connection (using GnuTLS). Ciphersuite (DTLS1.2)-(ECDHE-RSA)-(AES-256-GCM).
Configured as x.x.x.x + 2001:67c:10ec:578f:8000::1ee/115, with SSL connected and DTLS connected
Session authentication will expire at Wed, 31 Jan 2024 23:25:05 Pacific Standard Time
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
0: Waiting for existing driver to unload from kernel
0: Removing existing driver 0.8
0: Installing driver 0.14
0: Extracting driver
0: Installing driver
0: Creating adapter
Using Wintun device 'Local Area Connection 2', index 22
WARNING: Support for Wintun is experimental and may be unstable. If you
encounter problems, install the TAP-Windows driver instead. See
https://www.infradead.org/openconnect/building.html
Note: As a workaround, it seems possible to force OpenConnect to use a WinTAP network adapter (e.g. created by OpenVPN as well). This ensures that it doesn't interfere with OpenVPN.