[erlang-patches] [PATCH] epmd: support IPv6 node registration

[Michael Santos]

On Wed, Aug 19, 2015 at 09:34:38AM +0200, Dave Cottlehuber wrote:
> This is about Michael's (BCC'd) patch from 2013, lost in the space-time
> vortex:
> 
> 1st message
> http://erlang.org/pipermail/erlang-patches/2013-February/003585.html
> last message:
> http://erlang.org/pipermail/erlang-patches/2013-February/003585.html
> 
> the almighty github seems to think this is still mergeable:
> 
> https://github.com/erlang/otp/compare/maint...msantos:epmd-IPv6-node-reg
> 
> As I can't see anything in the discussion that blocks this, can we have
> it back please? IPv6 only is approaching (slightly faster than the heat
> death of the universe) and I'd like erlang to be ready too.
> 
> I actually ran into this the last couple of days and the way I worked
> around it was to create a local loopack 127.0.0.x address, and use this
> trick from Bob Ippolito:
> 
> ERL_EPMD_ADDRESS=127.0.0.1 erl -kernel inet_dist_use_interface
> "{127,0,0,1}" -name shell@REDACTED
> 
> It was on twitter but deserves to be easier to find in future than
> https://twitter.com/etrepum/status/198481550713692160

I've been hoping epmd will be re-written in Erlang as legend has long
foretold :)

I updated the patch back in February and tried to follow some of the
recommendations in RFC 4038:

    https://github.com/msantos/otp/commit/e17240ad822c5d834ed6d756e64b54348424eda2

    https://github.com/msantos/otp/tree/epmd6-dual-stack-wip

The changes were tested on Windows 2012. There were some build failures
on Windows before but I don't know how similar these environments are.

I'll see if the patch still applies to the latest erlang and submit a
pull request.