From owner-freebsd-current@FreeBSD.ORG Fri Apr 11 10:14:47 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 D66E637B401 for ; Fri, 11 Apr 2003 10:14:47 -0700 (PDT) Received: from imo-r05.mx.aol.com (imo-r05.mx.aol.com [152.163.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28AB743F85 for ; Fri, 11 Apr 2003 10:14:47 -0700 (PDT) (envelope-from BelletJr@aol.com) Received: from BelletJr@aol.com by imo-r05.mx.aol.com (mail_out_v34.21.) id e.113.21af9c71 (3310); Fri, 11 Apr 2003 13:14:14 -0400 (EDT) From: BelletJr@aol.com Message-ID: <113.21af9c71.2bc851e6@aol.com> Date: Fri, 11 Apr 2003 13:14:14 EDT To: barney@pit.databus.com MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: AOL 5.0 for Windows sub 116 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: Fri, 11 Apr 2003 17:14:48 -0000 >Dans un e-mail dat=E9 du 10/04/03 22:56:31 Paris, Madrid (Heure d'=E9t=E9),= =20 barney@pit.databus.com a =E9crit : > > >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= =20 >> unreachable because of an infinite loop in the routes? No time-out occurs= =20 and=20 >> 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. Thanks for your time. No, it happens well and truly with SOCK_STREAM. Jerome