From owner-freebsd-current@FreeBSD.ORG Sat Apr 12 01:33:00 2003 Return-Path: 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 3390E37B401 for ; Sat, 12 Apr 2003 01:33:00 -0700 (PDT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id E69EA43FBF for ; Sat, 12 Apr 2003 01:32:58 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 12 Apr 2003 09:32:58 +0100 (BST) Date: Sat, 12 Apr 2003 09:32:56 +0100 From: David Malone To: BelletJr@aol.com Message-ID: <20030412083256.GA28378@walton.maths.tcd.ie> References: <109.225ca595.2bc723f2@aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <109.225ca595.2bc723f2@aol.com> User-Agent: Mutt/1.5.3i Sender: dwmalone@maths.tcd.ie cc: current@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2003 08:33:01 -0000 On Thu, Apr 10, 2003 at 03:45:54PM -0400, BelletJr@aol.com wrote: > 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. I've tried connecting to a host which is unreachable in both 4.X and 5.X and in both cases connect returns an error with "Operation timed out". I wonder if you could post your source code and/or a tcpdump of what's actually sent and recieved over the network while this is happening? David.