public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin@cygwin.com
Subject: Re: Troubleshooting AutoSSH
Date: Fri, 12 Jul 2013 18:48:00 -0000	[thread overview]
Message-ID: <f7f0u8hgn9uc1r03vf8lctj3v0io4b10l8@4ax.com> (raw)
In-Reply-To: <Pine.BSO.4.53.1307121055000.32610@Mail.omnitec.net>

> debug1: Local connections to LOCALHOST:5661 forwarded to remote address
> 127.0.0.1:6661
> debug1: Local forwarding listening on ::1 port 5661.
> 				  ^^^^^^^^^
> 
> <connection attempt fails with "Connection closed by ::1">!!!!
> 
> It looks like the problem is that AutoSSH is binding to IPV6, *NOT*
> IPv4! sshd is set to "AddressFamily inet", .. so the problem appears to be
> that AutoSSH is not binding properly.
> 
> Don't see anything in the man pages or a quick search, .. how would one
> force AutoSSH to bind to IPv4? IPV6 is installed on this box, but not
> used.

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.

Does it help if you include the -4 switch to ssh, to force it to use ipv4
only?  It's worth a try.


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

  reply	other threads:[~2013-07-12 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12  0:52 L. V. Lammert
2013-07-12  7:37 ` Andrew Schulman
2013-07-12 16:47   ` L. V. Lammert
2013-07-12 18:48     ` Andrew Schulman [this message]
2013-07-12 19:15       ` L. V. Lammert
2013-07-12 19:18         ` Andrew Schulman
2013-07-12 21:19           ` L. V. Lammert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7f0u8hgn9uc1r03vf8lctj3v0io4b10l8@4ax.com \
    --to=schulman.andrew@epamail.epa.gov \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).