X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 8 Sep 2011 15:48:05 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Different error on socket while connecting to a box behind firewall Message-ID: <20110908134805.GC6163@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20110902095328.GD22172@calimero.vinschen.de> <124480922.20110905080856@mtu-net.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@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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