On Tue, May 12, 2015 at 07:47:39AM +0200, David Feugey wrote: > Perhaps you should mention which version of TAP you're using. > > Latest version 9.21.1 > > > Also attach the full log file to the thread. > > It is basically done. > The rest (AKA ...) is loadconfig lines, and OS lines. With no error.
Yes, those are what I want to see. Those lines were added to aid in reproducing the setup that the user has, a reproducable bug is one that's likely to get fixed rather than ignored. Please post the log on *all* issues reported. > Also *disable* windows firewall (or any third party firewall) and test. > > Already tested. No effect. > > 2) The version I'm using is 'TAP-Windows Provider V9' (Open VNP 2.1.3) > > Interesting. I read somewhere that with newer versions of OpenVPN, TAP > code was rewritten, and more strict on sync/async code (multiple commands > = async, even if you use sync functions... or something like this). Many > people seems to have problem to use it from their code. > > I tried with OpenVPN 2.1.3, and the TAP driver now works! Thanks. > Should I suggest an update? I'm now stuck with an old version of OpenVPN > (that I use for other purposes), including many flaws... Not very optimal > (but it works). Incidentally, now I know it causes an issue I'll see if I can add which version of the the TAP drier is in use to the log file .... I'll attempt to reproduce this with the new driver and see if there's a simple fix. Peter -- Peter Howkins [email protected] _______________________________________________ Rpcemu mailing list [email protected] http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
