Found the problem. tun-win32.c:45 -
#define TAP_COMPONENT_ID "tap0901"
This is only valid for the most recent version of the TAP adapter. For
other versions, this should actually be "tapoas". So openconnect
saying that there are no TAP adapters is incorrect. Instead, it should
check all known component IDs, and then check for the version, so that
instead of reporting no TAP adapters, it detects the following:
Error: TAP-Windows driver v9.9 or greater is required (found 9.7)
Set up tun device failed
On 17 April 2014 16:08, Greg Toombs <gtoombs at lakeheadu.ca> wrote:
> I'm fairly sure that the TAP driver is installed correctly:
>
> "C:\Program Files (x86)\OpenVPN Technologies\OpenVPN
> Client\core\openvpn" --show-adapters
> Available TAP-WIN32 adapters [name, GUID]:
> 'TAP Adapter' {443C9063-3FD4-498A-8D5A-A7578835D871}
>
> But then when I run openconnect, it seems to work up to here:
>
> ...
> Connected to HTTPS on xxxxxx.com
> Please enter your username and password.
> Username:xxxxxx
> Password:xxxxxx
> POST https://xxxxxx.com/+webvpn+/index.html
> Got CONNECT response: HTTP/1.1 200 OK
> CSTP connected. DPD 30, Keepalive 20
> Microsoft (R) Windows Script Host Version 5.8
> Copyright (C) Microsoft Corporation. All rights reserved.
>
> No Windows-TAP adapters found. Is the driver installed?
> Set up tun device failed
>
> Any idea what's up?
