public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@freemail.ru>
To: Corinna Vinschen <cygwin@cygwin.com>
Subject: Re: Different error on socket while connecting to a box behind firewall
Date: Mon, 05 Sep 2011 04:20:00 -0000	[thread overview]
Message-ID: <124480922.20110905080856@mtu-net.ru> (raw)
In-Reply-To: <20110902095328.GD22172@calimero.vinschen.de>

Greetings, Corinna Vinschen!

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


--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 05.09.2011, <08:04>

Sorry for my terrible english...


--
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:[~2011-09-05  4:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALRo7LvuQ_MjMw6cXC76-W4Q+MHoieRn-t=9OGTqvzSnncgmhA@mail.gmail.com>
2011-09-02  4:46 ` Jaswinder Bhamra
2011-09-02  9:54   ` Corinna Vinschen
2011-09-05  4:20     ` Andrey Repin [this message]
2011-09-08 13:49       ` Corinna Vinschen
2011-11-29  9:01 Jaswinder Bhamra
2011-11-29 15:57 ` Christopher Faylor

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=124480922.20110905080856@mtu-net.ru \
    --to=anrdaemon@freemail.ru \
    --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).