Date: Thu, 10 Apr 2003 16:56:04 -0400 From: Barney Wolff <barney@pit.databus.com> To: BelletJr@aol.com Cc: current@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts Message-ID: <20030410205604.GA8446@pit.databus.com> In-Reply-To: <109.225ca595.2bc723f2@aol.com> References: <109.225ca595.2bc723f2@aol.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. By any chance, are you using UDP (SOCK_DGRAM) rather than TCP (SOCK_STREAM)? That sets up data structures but sends no packets, so even if an icmp time-exceeded will be returned when you do send packets, the problem can't be detected yet. -- 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?20030410205604.GA8446>