Date: Sat, 12 Apr 2003 13:05:31 -0400 From: Barney Wolff <barney@pit.databus.com> To: David Malone <dwmalone@maths.tcd.ie> Cc: current@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts Message-ID: <20030412170531.GA60303@pit.databus.com> In-Reply-To: <20030412083256.GA28378@walton.maths.tcd.ie> References: <109.225ca595.2bc723f2@aol.com> <20030412083256.GA28378@walton.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030412170531.GA60303>