osiris
osiris copied to clipboard
Replication listener and ipv6
We are using rabbitmq in docker containers with dual stack ipv4 and ipv6 (ipv4 cannot be disabled in docker).
It looks like replication is listening to ipv4 by default:
$ ss -l -n -p
tcp LISTEN 0 128 0.0.0.0:4369 0.0.0.0:* users:(("epmd",pid=1577398,fd=3))
tcp LISTEN 0 0 0.0.0.0:6004 0.0.0.0:* users:(("beam.smp",pid=1577227,fd=38))
tcp LISTEN 0 128 *:5672 *:* users:(("beam.smp",pid=1577227,fd=44))
tcp LISTEN 0 128 *:25672 *:* users:(("beam.smp",pid=1577227,fd=17))
tcp LISTEN 0 128 *:2314 *:* users:(("beam.smp",pid=1577227,fd=42))
tcp LISTEN 0 128 *:5552 *:* users:(("beam.smp",pid=1577227,fd=43))
tcp LISTEN 0 128 [::]:4369 [::]:* users:(("epmd",pid=1577398,fd=4))
tcp LISTEN 0 128 *:15672 *:* users:(("beam.smp",pid=1577227,fd=41))
Is it possible that, at the moment, there is no listener option which would help us define the inet6
option ?
Hello! The fastest way for me to assist you is for you to provide a git repository containing a docker compose project that I can clone and run that contains the exact configuration you're using. I should be able to run docker compose up
.
Getting Erlang to work with IPv6 isn't straightforward.
Hello, I have added here an example running with the same configuration.
Maybe there is a way to tell the replication to use that erl_inetrc inet6
option ?
Any news about this?
@cosimomeli this is open source software released under a very permissive license, you are welcome to contribute to Osiris. Asking others to do the work you need is rude and not how open source software was designed to work.