> > This should be easy to test by editing the installed OemVista.inf (in > C:\Program Files\Tap-Windows\driver\ by default) and running addtap to create > a new adapter with the required iftype. The resulting interface will most > likely not show up in the adapter list in control panel, but should show in > 'openvpn --show-adapters’
Well, Win10 has very strict signing requirements and I have all secure boot enabled machines, so I’m not able to easily break them to test :) > > But I do not think it will work: with iftype = 0x83 (131) the interface will > not get a physical address (MAC) etc. Further, the tap-windows driver source > sets the iftype as IF_TYPE_ETHERNET_CSMACD (=0x06) which is supposed to match > the value in the inf file. That would explain why editing the registry after it’s installed to change the iftype does not work, if the driver itself is looking for the specific iftype. So I suppose there will have to be some further modification of the driver code to accommodate this. > > I have a couple of wifi only win10 machines on which I have not seen this > disconnection behaviour. Is it because I do not use redirect-gateway? Does > the wifi disconnection happen only when default route is overwritten or is > even "--redirect-gateway def1" not immune to it? I think it is due to the redirect-gateway, and def1 does not change the behavior. I believe it’s because Windows sends NCSI internet probes to determine if an adapter has “Internet” access. If you’re not redirecting your gateway, those probes will probably fail via the VPN interface so it won’t consider the VPN interface as a viable alternative. A frustrating part of the problem is that Windows overrides the routing table by *silently* directing new connections to the “better” Ethernet interface (in anticipation of the WiFi losing signal altogether, I suppose). The only way to observe this is to use the powershell command ‘find-netroute -remote <ip>’ which tells you where Windows will *really* send the packet. Also the effect of the redirection isn’t immediate, Windows waits from 30-120 seconds to start redirecting traffic to the VPN interface once it detects weak WiFi signal. Some more details of my setup: I use the Windows service-based VPN connection rather than user-initiated by way of openvpnserv2.exe. We are using build 1511 of Windows 10. I posted my configs here: https://forums.openvpn.net/viewtopic.php?f=4&t=24499 Thank you for taking the time to look at this. Karl Mueller ewi...@gmail.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
