-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> On Tue, 2014-09-30 at 15:18 +0300, Samuli Seppänen wrote: >>> Hi, >>> >>> On Tue, Sep 30, 2014 at 11:17:44AM +0300, Samuli Seppänen wrote: >>>> Just got more info from Thomas who's fixing the tap-windows6 issues. >>>> According to him most of the bugs are actually triggered by user-space >>>> code in OpenVPN 2.x which does not handle tap-windows errors correctly. >>>> He's working on that issue right now. >>> >>> Patches for the 2.x code welcome :-) - I have no idea what we do wrong, >>> as the whole "talk to a windows device driver" thing is magic for me. >>> >>> gert >> >> Apparently 2.x is not handling certain tap-windows6 return/error codes >> correctly. According to Thomas that is causing several of the issues >> we've experienced with tap-windows6. > > Do you have specifics, or should I wait for patches to land? I'll check > for similar problems in OpenConnect. > Quoting Thomas: "Incorrect handling error 995 in user-mode service is cause of _several_ of the remaining errors." - -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlQq0g4ACgkQwp2X7RmNIqOvWgCeKfUmF4swyG+naGR2+jLI02hU FR0AoJ77qs84Tuhj0RzD6WvbBjzQpWWf =6Nfw -----END PGP SIGNATURE-----
