From owner-freebsd-current@FreeBSD.ORG Sat Apr 12 10:05:33 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 8113437B401 for ; Sat, 12 Apr 2003 10:05:33 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE2A443FB1 for ; Sat, 12 Apr 2003 10:05:32 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h3CH5VdN060781; Sat, 12 Apr 2003 13:05:31 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h3CH5V50060780; Sat, 12 Apr 2003 13:05:31 -0400 (EDT) Date: Sat, 12 Apr 2003 13:05:31 -0400 From: Barney Wolff To: David Malone Message-ID: <20030412170531.GA60303@pit.databus.com> References: <109.225ca595.2bc723f2@aol.com> <20030412083256.GA28378@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030412083256.GA28378@walton.maths.tcd.ie> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) 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 17:05:33 -0000 On Sat, Apr 12, 2003 at 09:32:56AM +0100, David Malone wrote: > 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? The problem seems to be in the handling of the ICMP unreach-time-exceeded. See the PR I filed: http://www.freebsd.org/cgi/query-pr.cgi?pr=50839 I posted to -net because the problem is common to both stable and current. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.