This is the mail archive of the
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 13:49:59 -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>
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
Windows Firewall is not enabled, .. Trend Micro is installed, but I can
find no evidence it is more than virus scanner. The service user
(cyg_server) is a local Administrator, .. tried Administrator credentials,
but the service still cannot start if I try to force IPV4.
*User* level IPV4 connections (e.g. Firefox) are working, as I just did a
Cygwin reinstall to verify the situation.
Any thought on what might be blocking sshd from binding to the IPV4 stack?
FYI, this is the first machine we have used as a Domain Member, previously
we have only been running standalone; cyg_server is a local user, as is
our admin user.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple