[lkml]   [1999]   [Aug]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: connect() occasionally succeeds improperly to localhost port 1024-4999
"David S. Miller" wrote:

> Date: Sun, 29 Aug 1999 23:28:51 -0400 (EDT)
> From: Fyodor <>
> Sometimes a connect() to localhost will succeed even if there is no
> process listening on the port. This happens when the ephemeral
> local port selected by the kernel during the connect() happens to
> be the same port you are trying to connect to.
> Connecting to self is %100 legal behavior and has been a part of the
> BSD sockets API for years.

Eh? Sure you can listen on port X, call to port X, and succeed. Why does it
succeed when there is apparently nobody listening on port X?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:53    [W:0.049 / U:40.324 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site