Re: connect(2) behavior with unreacheable hosts

From: <BelletJr_at_aol.com>
Date: Fri, 11 Apr 2003 13:14:14 EDT
>Dans un e-mail daté du 10/04/03 22:56:31 Paris, Madrid (Heure d'été), 
barney_at_pit.databus.com a écrit :
>
>
>On Thu, Apr 10, 2003 at 03:45:54PM -0400, BelletJr_at_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.

Thanks for your time.
No, it happens well and truly with SOCK_STREAM.

Jerome
Received on Fri Apr 11 2003 - 08:14:47 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:03 UTC