Setting tunnel IP address fails on German Windows 7

[Martin Pauly]

On 02.07.2015 13:14, David Woodhouse wrote:
> On Tue, 2015-06-16 at 18:27 +0200, Martin Pauly wrote:
>> First, I suspected the language-dependent interface identifiers, but
>> with netsh you only get an "Element not found" when at least the
>> identifier exists (which is "LAN-Verbindung 3" in my case,
>> corresponding to "Local Area Connection 3".
>
> I'm assuming this is the machine you sent the registry dump from? On
> another machine it was named 'Ethernet 2', yes?
yes, I used the second machine ony to have a cross check with German 64 Bit
(a depency here would have been really weird, though, but you never know)


> How was the TAP driver installed? Normally it gets a name like
> 'TAP-Windows Adapter V9'. That doesn't naturally translate to
> 'LAN-Verbindung 3'.
we downloaded and smoothly installed
https://github.com/openconnect/openconnect-gui/releases/download/v1.3/openconnect-installer.exe
I cannot preclude an earlier manual installation of th eopenvpvn TUN/TAP driver, though.
We had done some experiments with earlier versions of openconnect-gui.
  

> It is 'LAN-Verbindung 3' which is displayed in the control panel if you
> go to the adapter settings? If you rename it there, do things change?
yes, renaming it to "TAP" results in successful setting of the IP address
as shown by ipconfig.
  
> Is it possible to work out what name *does* work with 'netsh' for this
> device?

------- netsh show with old Adapter Name "Lan-Verbindung 3" --------------------

C:\Users\martin\Documents>netsh int sh int

Verw.-status   Status         Typ              Schnittstellenname
-------------------------------------------------------------------------
Deaktiviert    Getrennt       Dediziert        Cisco AnyConnect Secure Mobility Client Connection
Aktiviert      Getrennt       Dediziert        LAN-Verbindung 3
Aktiviert      Getrennt       Dediziert        LAN-Verbindung
Aktiviert      Getrennt       Dediziert        Drahtlosnetzwerkverbindung


C:\Users\martin\Documents>netsh int sh int "Lan-Verbindung 3"

LAN-Verbindung 3
    Typ:                  Dediziert
    Verwaltungsstatus:    Aktiviert
    Verbindungsstatus:    Getrennt

------- End of netsh show with old Adapter Name "Lan-Verbindung 3" --------------------

- Use Network settings (ncpa.cpl) to rename adapter to "TAP"

------- netsh show with new Adapter Name "TAP" -------------------
C:\Windows\system32>netsh int sh int

Verw.-status   Status         Typ              Schnittstellenname
-------------------------------------------------------------------------
Deaktiviert    Getrennt       Dediziert        Cisco AnyConnect Secure Mobility Client Connection
Aktiviert      Getrennt       Dediziert        TAP
Aktiviert      Verbunden      Dediziert        LAN-Verbindung
Aktiviert      Getrennt       Dediziert        Drahtlosnetzwerkverbindung


C:\Windows\system32>
C:\Windows\system32>
C:\Windows\system32>netsh int sh int TAP

TAP
    Typ:                  Dediziert
    Verwaltungsstatus:    Aktiviert
    Verbindungsstatus:    Getrennt

-------End of netsh show with new Adapter Name "TAP" -------------------


So looks like it's really all about the adapter name chosen by some Windows magic.
In my Opinion, setting the name explicitly to something clear like "TUN/TAP openvpn/openconnect"
would help anyway. You could tell adapters apart much easier then.
BTW, manually calling openvpn's
%ProgramFiles%\TAP-Windows\devcon.exe install "addtap.bat" (which in turn calls devcon.exe)
results in another "LAN-Verbindung 3" (the name was no longer occupied because of the above rename).

> But looking at your registry files, it definitely looks like that's
> what it's called. Does OpenVPN fare any better? If you run
> 'openvpn --show-adapters' what name does it give?
going to try that later today.

Martin
-- 
   Dr. Martin Pauly     Phone:  +49-6421-28-23527
   HRZ Univ. Marburg    Fax:    +49-6421-28-26994
   Hans-Meerwein-Str.   E-Mail: pauly at HRZ.Uni-Marburg.DE
   D-35032 Marburg