Opened 4 years ago
Closed 3 years ago
#1237 closed Bug / Defect (wontfix)
Network Connection created by OpenVPN CLient 2.4.8 in Windows 10 1809 isn't fully recognized
| Reported by: | mrosen | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | release 2.4.8 |
| Component: | Networking | Version: | |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
| Cc: | tap-windows6, zenworks, location, detection |
Description
We are Using Microfocus Zenworks in our environment, which has a functionality to detect "locations" based on certain parameters of the local network connection, in our case, simply by the ip address range. E.G, when a machine has a IP in the 172.30.1.0/24 network, then we consider this the location "VPN" and can act upon that.
Immediately after updating OpenVPN client 2.4.7 to 2.4.8, this stopped working. Downgrading to 2.4.7 makes it work again.
The only other hint I found that is different and maybe related is that with 2.4.8, Windows shows the openvpn adapter in ipconfig /all as ""Unbekannter Adapter Lan-Verbindung" ("Unknown Adapter Lan-Connection", my translation), whereas in 2.4.7 it's called "Ethernet-Adapter Ethernet 2"
Change History (1)
comment:1 Changed 3 years ago by
| Cc: | tap-windows6 zenworks location detection added |
|---|---|
| Keywords: | W removed |
| Resolution: | → wontfix |
| Status: | new → closed |
The TAP driver was changed from claiming "I am an ethernet driver" to "I am a virtual interface" - which was right before 2.4.8 release.
I don't think there is anything we can do about it on the OpenVPN side (except "revert that change", but we had quite some discussion about it and the end result was "this is more correct behaviour"). The PR is here: https://github.com/OpenVPN/tap-windows6/pull/84
So - I think you'll need to open a ticket with Microfocus about this, so they can recognize virtual interfaces as well.
I will proceed to close the ticket as "wontfix", as this is not something we can fix on our end.