Hi there
I just heard from one of our IS staff who moved onto the Win10 Insider
build 14332 that it was continually bluescreening - ended up disabling
openvpn fixed it (we run openvpn as a service). So I did the same thing
(installed 14332) using the current 2.3.11-I601-x86_64 and indeed the
moment the TAP interface comes up (ie it gets a tunnel IP address), the
system crashes. This issue also affects the older 2.3.10 version - so it's
more likely the new Win10 build "does something differently"
So this could be a major bug with Win10 14332 (it only just came out) that
openvpn just happens to tickle - but it could also imply Win10 now has some
subtle assumptions that openvpn/TAP isn't meeting?
I dunno - that's why I brought it up :-)
PS: The bluescreen only says "CRITICAL_PROCESS_DIED" and there's nothing in
the eventlog about it. System comes up, openvpn is started, openvpn logs
get to report "Initialization Sequence Completed", system crashes.
--
Cheers
Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +1 408 481 8171
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
