You should try using the older TAP-Win32 drivers that are bundled with tinc (i.e. 9.0.0.9). Using the newer, NDIS6 drivers (>= 9.0.0.21) is not recommended; according to some testing I did in the past it seems to result in poor tinc performance (for reasons I wasn't quite able to determine). I am using tinc 1.1 with 9.0.0.9 on Windows 10 and it behaves correctly when returning from standby.
On 23 August 2016 at 14:10, [email protected] <[email protected]> wrote: > Hello, > > I am using tinc for about two years now, and server-side everything is > perfect. But on my Windows 10 computer using tinc 1.1 and the OpenVPN TAP > Provider 9.0.0.21 I always have to shutdown and restart the tinc service, > when the computer returns from standby or hibernation. This problem is not > related to the recent Windows updates. > > I am using > Mode = switch > ExperimentalProtocol = no > > Depending on the other settings, I sometimes see errors like "Metadata > socket read error for <control>" or "Error while writing to TAP device..." > > Right now I have the Metadata error, and log just shows an ongoing stream > of "Sending UDP probe length 18" to the various ConnectTo hosts. > > I would like to know, if reconnecting to tinc automatically works for > other users on Windows 10 and if there is some recommended configuration? > > Thanks for any advice, or workaround, > > Karel > > _______________________________________________ > tinc mailing list > [email protected] > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > >
_______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
