Open zingmars opened 5 years ago
Do we have the same problem in the stable version of tinc?
@fangfufu Not sure, haven't tried it since I exclusively use 1.1 because it has many features 1.0 does not. My current "fix" is a scheduled task that fires after waking up that will simply kill tinc and start it again.
On Windows 10 v1903 using Tinc1.1pre17 and the TAP drivers shipped with this version.
After waking up from hibernation tinc reconnects, but I'm unable to either ping or connect to any device connected (connection timed out). What's weirder, when I try to restart or turn tinc off, it will no longer terminate nicely and I have to terminate the process. Here's a log with -d3:
(Also I have no idea why it won't connect to anotherdevice. It connects just fine after I ping it or attempt to connect to it's address using any software, but if I don't it just keeps trying to connect and failing like this).
At the end the "Console shutdown request" entries are caused by me spamming ctrl+c in the console window trying to stop it. In this state the only way to actually stop Tinc is to either close the console window (not an option if started as a service) or kill its process. The only thing that has changed altely is me setting manual metric values for the tinc interface so that Windows would use a DNS server exposed to the Tinc network, but even then it took a while for this to start happening so I'm not sure if it's related.