Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#829 closed Bug / Defect (notabug)

hdwwiz -> new tap adapter , doesn't work

Reported by: titex Owned by:
Priority: minor Milestone:
Component: tap-windows Version: OpenVPN 2.4.0 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords: windows10 tap hdwwiz
Cc: Samuli Seppänen

Description

If you add a new tap adapter with hdwwiz on Windows, openvpn doesn't see it as available

Wed Jan 25 09:58:47 2017 All TAP-Windows adapters on this system are currently in use.
Wed Jan 25 09:58:47 2017 Exiting due to fatal error

openvpn --version
OpenVPN 2.4.0 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Dec 27 2016

Windows 10 x64 Enterprise

Change History (6)

comment:1 Changed 3 years ago by Gert Döring

Cc: Samuli Seppänen added

Well - whatever hdwwiz is, it seems it's not installing the tap adapter with the GUIDs that we need to see to identify it as such.

Can you provide the output of "ipconfig /a" and an openvpn log with --verb 4 to show a bit more detail?

comment:2 Changed 3 years ago by TiTex

hdwwiz is the old hardware wizard https://msdn.microsoft.com/en-us/library/windows/hardware/ff553639%28v=vs.85%29.aspx

i uploaded a video here https://youtu.be/dsImZ46PvxQ , not the best quality but it's visible what's happening.
It only shows the single TAP adapter because the one installed with openvpn is disabled as you saw in the video

PS C:\Users\Administrator> ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : WIN-MEQ59VIAT26
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . :

Ethernet adapter TAP01-HDWWIZ:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Windows Adapter V9 #2
Physical Address. . . . . . . . . : 00-FF-2B-CB-15-3A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Here is more info using powershell's Get-NetAdapter? http://pastebin.com/dyVCcN0y

And here is the log at verb4 http://pastebin.com/7BwJAHBG

comment:3 Changed 3 years ago by Samuli Seppänen

Out of curiosity: why do you want to use hdwwiz to install new tap-windows6 adapters?

That aside, can you try the following commands:

cd 'C:\Program Files\OpenVPN\bin'
.\openvpn --show-adapters
.\tapinstall.exe hwids tap091

What do they output?

comment:4 Changed 3 years ago by TiTex

I don't want to use hdwwiz per say , one time i wanted to add a new tap adapter but i couldn't find that batch script which was used to add one so i used the hdwwiz , i knew that it worked at one time because i used it before in the past.

If it's too much hassle , i guess we can just close this issue and everybody should use the batch script provided :)

C:\Program Files\OpenVPN\bin>openvpn --show-adapters
Available TAP-WIN32 adapters [name, GUID]:
'TAP01-OVPN INSTALL' {FFF1F0A2-932A-406F-AB90-4E627F0D6CC6}
C:\Program Files\TAP-Windows\bin>tapinstall.exe hwids tap*
ROOT\NET\0000
    Name: TAP-Windows Adapter V9
    Hardware IDs:
        tap0901
1 matching device(s) found.

C:\Program Files\TAP-Windows\bin>                             

comment:5 Changed 3 years ago by Samuli Seppänen

Resolution: notabug
Status: newclosed

Neither openvpn nor tapinstall.exe seem to see the hdwwiz-generated tap-adapter. I suspect hdwwiz relies on OemVista.inf having the installation "recipe", which is missing, as we've always let the batch script handle installation.

I'll close this a notabug. Thanks for reporting this, though!

comment:6 Changed 3 years ago by TiTex

okay , no problem

Note: See TracTickets for help on using tickets.