X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; q=dns; s=default; b=YSjYF r0HOX4sopBeXMfik4d2Vk91uy0jpS//tH395cr8RxDUFIRhA8HtqzD6MDAleMtY7 HCNtfLKo1ezlrxeipBJCptCoYNnYs+YJ2YrZ/8uhJlYGHWFhH8knWEb9ZL8GwD0/ ddZIdvyVeoLsUshXv9VOKYN4XsXHPxerxvxHw4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; s=default; bh=ti66l440A5K wMUrQsf37C2OxbnI=; b=uk9sPtrmda4PFZ2fiaTYd7fvG+ud9BXVShhSVrsVEky GCLjbn+3Q86u4AWWvYOdz324/RJ9y3wxjvU0WdTZ/1PJMGmwwnb5yHkGX9LiEuZW 1w+/p6Vq/HKxzN5H44bRTNpCAbhfBpdZ3qikytbIfyWvsD0WONQWNrz2TdBXa568 = Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RDNS_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 Date: Fri, 12 Jul 2013 15:17:17 -0500 (CDT) From: "L. V. Lammert" To: Andrew Schulman cc: cygwin AT cygwin DOT com Subject: Re: Troubleshooting AutoSSH In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SPAM-Info: Omnitec Corporation MailScanner X-SPAM-MailScanner: Found to be clean 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