connect(2) behavior with unreacheable hosts
Barney Wolff
barney at pit.databus.com
Sat Apr 12 20:05:06 PDT 2003
On Sat, Apr 12, 2003 at 08:49:12PM -0600, M. Warner Losh wrote:
> In message: <109.225ca595.2bc723f2 at aol.com>
> BelletJr at aol.com writes:
> : Why does not connect(2) return any error when trying to connect to a host
> : unreachable because of an infinite loop in the routes? No time-out occurs and
> : the value 0 is returned by connect(2).
>
> Hmmmmm, you are correct. I was sure that you were nuts, but on
> -current the following program returns no error at all... Telnet
> shows the same behavior. This is clearly wrong.
It's not just current; stable behaves exactly the same. The problem is
that the icmp time-exceeded packet gets translated into an error code
of 0, which confuses things. I've filed a PR with a suggested fix:
http://www.freebsd.org/cgi/query-pr.cgi?pr=50839
--
Barney Wolff http://www.databus.com/bwresume.pdf
I'm available by contract or FT, in the NYC metro area or via the 'Net.
More information about the freebsd-current
mailing list