New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to reconnect when remote host referenced via (dynamic) dns #110
Comments
Allow connection_fatal to trigger a reconnect attempt, which, if there is still an issue, which eventually call connection_fatal. This causes us to retry indefinitely. Maybe eventually we'll need to limit this somehow (exponential backoff?). Also: * Remove wakeup reconnect delay. Infinite reconnects will fix this itself. * Make a dns error a normal connection_fatal. Oh dear, oh dear. This was hardcoded to just messagebox and outright exit(0);. Now we keep going for a tiny bit, so that we can run the normal cleanup code. This is the tiny cleanups to ssh.c.
You've done it now. Whole load of horrors in that commit which should fix this (among other things). You need to turn on both reconnect modes to get everything to "work". See the commit. |
Thanks! Seems to work fine now... As you hinted to in your commit, it might be nice to be able to control the rate at which it tries to reconnect. |
PuTTYTray reconnects just fine when my host name is found in my Windows hosts file.
However, when I use a remote host name that uses (dynamic) DNS (e.g., mymachine.dyndns.org), it times out with the following error message:
Pressing "OK" (the only option), then causes PuTTYTray to exit.
Shouldn't PuTTYTray realize that the non-existence of a host (presumably non response from a dns-type query) is exactly what one would expect when the Internet connection is down... so that PuTTYTray should continue waiting to reconnect rather than throwing an error message and exiting
The text was updated successfully, but these errors were encountered: