On Mon, May 04, 2015 at 11:59:44AM +0000, Chris Haaser wrote: > it's been a while, but I have finally gotten around to testing that. > The problem does not seem to be tinc itself, but the TAP adapter. Tinc writes > key exchanges and packets and so on into its log, but Windows seems to have > forgotten all about the tinc adapter - ipconfig does not show an entry for > it, there are no routes for it etc. > Just opening the TCP/IP properties in control center brings the connection > back up. > > Since the Win-TAP driver bundled with tinc seems to be quite old, I will try > upgrading that from the OpenVPN site and see if it runs more stable.
You might need to run deltapall.bat and then addtap.bat to get a fresh
TAP interface.
Did you do any software upgrades around the time tinc stopped working?
Windows shouldn't forget about a network adapter without a reason.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
