X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Thu, 8 Sep 2011 15:48:05 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Different error on socket while connecting to a box behind firewall
Message-ID: <20110908134805.GC6163@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CALRo7LvuQ_MjMw6cXC76-W4Q+MHoieRn-t=9OGTqvzSnncgmhA AT mail DOT gmail DOT com> <CALRo7LvM8ABqKntq7X1vMkhssHz1UMBmw=3FN2GFAo9paE5YuQ AT mail DOT gmail DOT com> <20110902095328 DOT GD22172 AT calimero DOT vinschen DOT de> <124480922 DOT 20110905080856 AT mtu-net DOT ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <124480922.20110905080856@mtu-net.ru>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Sep  5 08:08, Andrey Repin wrote:
> > However, even with this fix, you might not get EHOSTUNREACH either.  In
> > my testing, the error returned by the underlying Winsock getsockopt
> > function is not WSAEHOSTUNREACH, but WSAETIMEDOUT.  This will be
> > translated into ETIMEDOUT == "Connection timed out".
> 
> To clarify, and what I think is important to understand, is that the "Host
> unreachable" error status could only be triggered by the parent router
> returning an explicit "not reachable" reply to a connection attempt. But since
> this reply is an ICMP message, many poorly configured intermediate routers,
> like home firewalls, could block it and you will get the WSATIMEDOUT for no
> apparent answer from the remote host in time.

This was a pure local test, trying to connect to an unused port on a
Linux machine.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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