[erlang-questions] Distributed Erlang transport over SSL

Serge Aleynikov serge@REDACTED
Thu Oct 24 15:07:01 CEST 2013

I've been experimenting with starting Erlang distribution with both TLS and
TCP distributed transports as the "-proto_dist" option allows to specify
multiple modules handling distributed transport setup, but stumbled across
the fact that when both inet_tls and inet_tcp is specified, it fails to
register the second transport with EPMD.

I think the answer is no, but is there a way to tell EPMD that the same
node can have more than one port registered for a given node per protocol
it supports?

If it's not possible, maybe I would need to roll out a custom distributed
transport handling module that would conditionally upgrade the incoming
connection from TCP to SSL based on some user-logic (e.g. if a node doesn't
belong to a local cluster).  Has anyone done anything similar?

On Mon, Oct 21, 2013 at 12:39 PM, Motiejus Jakštys <desired.mta@REDACTED>wrote:

> On Mon, Oct 21, 2013 at 5:56 PM, Serge Aleynikov <serge@REDACTED>
> wrote:
> > seem to be any documentation of if it's possible to give hints to a given
> > node to use transport alternative to the one used by current node at
> startup
> > when connecting to given nodes.
> >
> > If this is not supported, I would opt for this feature request as this
> seems
> > to be a very general case when running node configurations spanning
> multiple
> > clusters.
> Hi,
> See Patrick Nyblon's reply to a similar question:
> http://erlang.org/pipermail/erlang-questions/2012-October/069876.html
> From the last paragraph I infer that what you are trying to do is
> supported or easily supportable (lacks details though).
> --
> Motiejus Jakštys
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20131024/8c9fc784/attachment.htm>

More information about the erlang-questions mailing list