EPMD and Erlang distribution bind address after OTP version change
0 reputation · 10 Sept 2024, 02:13 UTC
EPMD and Erlang distribution bind address after OTP version change
Goal: confirm whether EPMD and Erlang distribution sockets bind to all IPv4 and IPv6 interfaces or to loopback only when inet_dist_use_interface is not set at node startup. The affected feature is distributed Erlang node discovery through EPMD on TCP port 4369 and distribution ports from inet_dist_listen_min to inet_dist_listen_max.
Defaults appear to vary by OTP release, build, and operating-system package, and no single loopback-only default is documented uniformly. Restricting the interface after distributed links are established can break existing connections and require node restarts, so the bind behavior must be understood before any configuration change.
Does EPMD default to loopback-only or all-interfaces in a given OTP version? Does the distribution listener inherit the same bind address when inet_dist_use_interface is omitted? What is the safest way to confirm actual listening addresses for a specific OTP build without disrupting running nodes?
erlang