IPv6 incorrect setup (or resolver bug? or http client bug?)

[Ingela Anderton]

Sean Hinde wrote:
> 
> On 2 Nov 2004, at 08:07, Ingela Anderton wrote:
> 
> >
> > Matthias Lang wrote:
> >>
> >>  Matthias> Is 172.16.2.2 an ip6 address?
> >>
> >>  Ingela> No, it is a ipv4 address.
> >>
> >> Come to think of it, what does
> >>
> >>  inet:getaddr("localhost", inet6)
> >>
> >> return?
> > 2>  inet:getaddr("localhost", inet6).
> > {ok,{0,0,0,0,0,65535,32512,1}}
> > 3> inet:getaddr("localhost", inet).
> > {ok,{127,0,0,1}}
> 
> Interesting. on Mac OS X:
> 
> 1> inet:getaddr("localhost", inet6).
> {ok,{0,0,0,0,0,0,0,1}}
Well on any machine that acctualy support ipv6:

$ erl
Erlang (BEAM) emulator version 5.4.1 [hipe] [threads:0] [kernel-poll]

Eshell V5.4.1  (abort with ^G)
1>  inet:getaddr("localhost", inet6).
{ok,{0,0,0,0,0,0,0,1}}
2> 

On a machine that does not

$ erl
Erlang (BEAM) emulator version 5.4.1 [hipe] [threads:0] [kernel-poll]

Eshell V5.4.1  (abort with ^G)
1>   inet:getaddr("localhost", inet6).
{ok,{0,0,0,0,0,65535,32512,1}}
2> 

I guess that would be the ipv6 tunneled version of the ipv4 address
127.0.0.1. 

-- 
/Ingela

Ericsson AB - OTP team