Hey, 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. Best regards, Chris -----Ursprüngliche Nachricht----- Von: tinc [mailto:[email protected]] Im Auftrag von Guus Sliepen Gesendet: Mittwoch, 18. März 2015 19:31 An: [email protected] Betreff: Re: Tinc connection does not come up when started as Windows service On Wed, Mar 18, 2015 at 12:10:40PM +0000, Chris Haaser wrote: > I have a tinc mesh consisting of 6 Windows servers. All are configured > identically and all but one work without any problems. > On that one server however the tinc service starts, but the connection does > not come up (no packets get routed, ping times out). > If I stop and start the service manually, the connection is up in like half a > second. If I start tinc on the command line, it works every time. > > Is there anything I can do to debug tinc when running as a service? I tried > setting it to startup automatically / delayed, but that didn't work either. The easiest way is to tell tinc to log to a file. Start it like this: tincd -n <netname> --logfile=C:\Temp\tinc.log -d5 Then check what is in the logfile. -- Met vriendelijke groet / with kind regards, Guus Sliepen <[email protected]> _______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
