hi all,
in the eduVPN project we've run into a strange issue:
HP Envy laptops running Windows 10 have a "handy" feature to
automatically switch from wifi to a 'wired' adapter if one is detected.
The use case behind this is that if you put your laptop in a docking
station (with LAN) it will auto-switch to it.
How does this relate to OpenVPN: when an OpenVPN connection is
established, the HP Envy driver gimmick detects the tap-windows device
as a LAN adapter and switches off wifi -regardless of whether you are on
a LAN or not. Thus, "plain" OpenVPN 2.4 becomes quite hard to use on
these laptops.
Now the strange part is, that both Viscosity and NordVPN - each with
their own tap-win adapters do NOT have this problem.
So my question now is: what could be causing this and how can we
resolve it.
The patches the Viscosity folks made to the tap-win driver for their
setup are in github (pull request #47, IIRC) and I don't see anything
truly strange in that patch.
The only thing that seems to be different is whether a device is
sporting the UI flag in the "characterstics" section.
Does anybody have a clue how to best approach this?
thx,
JJK
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
