[erlang-questions] inet:getaddr different results in two different erlang nodes (same machine)

[Attila Rajmund Nohl]

Probably the same "feature". Use the tuple format everywhere you can.
Then fix the bugs where you've used ++ to create an error message with
the IP address.

2009/6/29, Enrique Marcote <mpquique@REDACTED>:
> Sorry, R13A.
>
> El 29/06/2009, a las 14:11, Attila Rajmund Nohl escribió:
>
>> 2009/6/29, Enrique Marcote <mpquique@REDACTED>:
>>> Hi,
>>>
>>> I have two erlang nodes running simultaneously on the same machine
>>> (windows 2003 server).
>>>
>>> In one of them I get:
>>>
>>> (ssentinel@REDACTED)49> gen_tcp:connect({192,168,2,32}, 2200,
>>> [inet], 3000).
>>> {ok,#Port<0.1796813>}
>>> (ssentinel@REDACTED)50> gen_tcp:connect("192.168.2.32", 2200,
>>> [inet], 3000).
>>> {error,timeout}
>>> (ssentinel@REDACTED)51> inet:getaddr("192.168.2.32", inet).
>>> {error,timeout}
>>
>> Isn't it R13B? In my experience R13B tends to handle the
>> "192.168.2.32" string as an IPv6 address (or something like this).
>
>