This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Troubleshooting AutoSSH
- From: "L. V. Lammert" <lvl at omnitec dot net>
- To: Andrew Schulman <schulman dot andrew at epamail dot epa dot gov>
- Cc: cygwin at cygwin dot com
- Date: Fri, 12 Jul 2013 15:17:17 -0500 (CDT)
- 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> <d1l0u8t2ccbedj8tk8vg594lam0k4svpgp at 4ax dot com>
On Fri, 12 Jul 2013, Andrew Schulman wrote:
> > 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?
>
I did not try forcing -6 because that was the only way it would connect
(i.e. sshd would only start with an IPV6 connection, forcing IPV4 was a
non-starter).
> If sshd is only accepting ipv6, then it may be autossh's port monitoring
> feature that's broken.
>
The failure is in starting sshd, so it's something in the OpenSSH update
(15 May), or something in this Windows machine.
> 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?
>
I could try, but there is no way I can test a remote connection with V6,
local connections on V6 do work when using default configuration.
Would there be any value in testing the previous package, openssh-6.2p1-2?
Lee
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple