[erlang-questions] TCP Kernel bug/feature

Javier París <>
Thu May 17 14:06:24 CEST 2007


El Thursday 17 May 2007 13:18:24 Martin Carlson escribió:

Hi,

> When running node1() on one Erlang node and node2 on another
> this creates a socket connected to itself. One can capture the socket and
> pass data forth and back.
>
> netstat gives the following result:
> tcp        0      0 127.0.0.1:12345         127.0.0.1:12345
> ESTABLISHED
>
> This however only seem to work on Suse 9.3 with a stock kernel and has
> probably been fixed in newer versions of the kernel.

Well, as far as I know, this is not against the RFC, so there isn't any reason
why it shouldn't work. It's curious, tough :)

Regards.

-- 
Javier París




More information about the erlang-questions mailing list