From owner-freebsd-current@FreeBSD.ORG  Thu Apr 10 12:46:31 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D304337B41B
	for <current@freebsd.org>; Thu, 10 Apr 2003 12:46:31 -0700 (PDT)
Received: from imo-d05.mx.aol.com (imo-d05.mx.aol.com [205.188.157.37])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D575943F85
	for <current@freebsd.org>; Thu, 10 Apr 2003 12:46:30 -0700 (PDT)
	(envelope-from BelletJr@aol.com)
Received: from BelletJr@aol.com
	by imo-d05.mx.aol.com (mail_out_v34.21.) id n.109.225ca595 (3842)
	 for <current@freebsd.org>; Thu, 10 Apr 2003 15:45:55 -0400 (EDT)
From: BelletJr@aol.com
Message-ID: <109.225ca595.2bc723f2@aol.com>
Date: Thu, 10 Apr 2003 15:45:54 EDT
To: current@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 116
Subject: connect(2) behavior with unreacheable hosts
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2003 19:46:32 -0000

Hi all,

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).
My test was done with TCP/IPv4.

Jerome