Our ipv6 enabled check returns false on Ubuntu

[mmzeeman]

My plain ubuntu dev machine has ipv6 enabled, but zotonic returns false on its ipv6 enabled check. This check tries to get the ipv6 address for localhost. But on Ubuntu it returns::

1> inet:getaddr("localhost", inet6).
{error,nxdomain}
2> inet:getaddr("ip6-localhost", inet6).
{ok,{0,0,0,0,0,0,0,1}}

Is this a ubuntu configuration error and should ::1 localhost be added to the hosts file? Or do we have to make a better ip6 enabled check?

[mworrell]

I think we can do an extra lookup as fallback. This check is a heuristic anyway.

[mmzeeman]

Hmm, other things go wrong when I check for ip6-localhost. Binding to any6 goes wrong later on then. Currently zotonic expects localhost to be an ip4 and ip6 name.

BTW Does anybody currently use zotonic in production with ip6?

[CyBeRoni]

BTW Does anybody currently use zotonic in production with ip6?

That is irrelevant, all software should support IPv6.

Also, since I make a point out of our services being IPv6-enabled: yes, but since I stick everything behind haproxy, zotonic does not itself bind to v6 sockets for me.

[mmzeeman]

I was busy with the ssl issue, which of course also covers IPv6. I wanted to test this in practice on a real server. Because I don't have a big array of servers available I have to work with what I got. This is a Shuttle XS35V4 sitting behind a fritzbox at home on fiber-optics.

On my internal network it speaks IPv6, but for some reason I can't make it available on IPv6 on the external network. The configuration interface of the fritzbox uses IPv4 NAT and port-mapping terminology, which is a bit strange.

Anyhow, I was just wondering how well zotonic works on IPv6.

[CyBeRoni]

Anyhow, I was just wondering how well zotonic works on IPv6.

I can set up a vm for you to try it with for a bit if you want.

[mworrell]

This doesn't seem to be a problem anymore on current systems?

@CyBeRoni or @mmzeeman can you confirm this?