This is the mail archive of the
mailing list for the Cygwin project.
Re: Troubleshooting AutoSSH
- From: Andrew Schulman <schulman dot andrew at epamail dot epa dot gov>
- To: cygwin at cygwin dot com
- Date: Fri, 12 Jul 2013 15:15:02 -0400
- Subject: Re: Troubleshooting AutoSSH
- References: <Pine dot BSO dot 4 dot 53 dot 1307111701260 dot 32610 at Mail dot omnitec dot net> <tm1vt8pl995u8nvkpebtmbrc0tq3jjmggh at 4ax dot com> <Pine dot BSO dot 4 dot 53 dot 1307121055000 dot 32610 at Mail dot omnitec dot net> <f7f0u8hgn9uc1r03vf8lctj3v0io4b10l8 at 4ax dot com> <Pine dot BSO dot 4 dot 53 dot 1307121338440 dot 32610 at Mail dot omnitec dot net>
> On Fri, 12 Jul 2013, Andrew Schulman wrote:
> > Hi Lee. Okay, that does seem to narrow it down.
> > You're right that autossh doesn't have any ipv4 options. It hasn't been
> > updated in a few years, and I think it's just not ipv6-aware yet.
> Looks like it may not be autossh - if I start sshd with a default config,
> it works [ssh localhost], .. if I try ssh -4 localhost, nada!
> It looks like *sshd* can only bind IPV6 - forcing it to bind IPV4 only
> prevents startup.
OK. So does it work then to pass the -6 flag to ssh?
If sshd is only accepting ipv6, then it may be autossh's port monitoring
feature that's broken. It uses ssh to forward some ports of its own, and
that feature might be ipv4-only. You can turn it off by passing -M0 to
autossh. Does that fix the problem?
If that does fix the problem, then it's not a very good solution, because
you've had to disable autossh's monitoring of your connection. So it won't
know if your connection has stopped passing traffic, in order to restart
it. But at least we'll have a well-defined bug to report upstream.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple