DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=UnTdRXDvwy+Z/K/ebflzH7UfBC4lRt5ooOHf1lLuKSGksHGQsURzU
	9j1lgzTOkmmDN+S9q6wAJFdX3gc82VMv4GE7ywY3eu0gUjPeaOmdrE7N8fvwKpYG
	4CY+lvDWEY7F0Rdtik8eAil6HrKTwpvCo0sBWZ8yvZ4uN/O5iSPcjo=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
Subject: Re: Troubleshooting AutoSSH
Date: Fri, 12 Jul 2013 15:15:02 -0400
Lines: 26
Message-ID: <d1l0u8t2ccbedj8tk8vg594lam0k4svpgp@4ax.com>
References: <Pine.BSO.4.53.1307111701260.32610@Mail.omnitec.net> <tm1vt8pl995u8nvkpebtmbrc0tq3jjmggh@4ax.com> <Pine.BSO.4.53.1307121055000.32610@Mail.omnitec.net> <f7f0u8hgn9uc1r03vf8lctj3v0io4b10l8@4ax.com> <Pine.BSO.4.53.1307121338440.32610@Mail.omnitec.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> 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.

Andrew


--
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