Default to listening on ::

[laurivosandi]

Currently following is required to make Dragonfly operator work IPv6 only or dual stacked environments:

  args:
    - "--bind=::"
    - "--admin_bind=::"

As the day of CONFIG_IPV4=n is getting closer by every day I would suggest switching listening from 0.0.0.0 to :: in Dragonfly binary itself

This is compatible with all modes IPv4-only, IPv6-only and dual stack

[vyavdoshenko]

@laurivosandi
Thanks for reporting the issue.

[JDucr17]

Hi, i'd like to contribute to this issue if possible.

The approach i have in mind is to use IPv6 wildcard listener sockets for automatic binding on both the main and admin ports, falling back to IPv4 when IPv6 is unavailable. I'd preserve explicit bind addresses and the existing systemd protected mode behavior.

If this is the correct approach, should the listeners explicitly set IPV6_V6ONLY=0 to ensure dual stack operation, or inherit the OS default even when that results in IPv6 only listening?

If there are any other considerations i need to keep in mind i'd be glad to know, thanks!

[romange]

1. We should not override IPV6_V6ONLY from Dragonfly.
2. Our production environment runs dual-stack, so we should really understand the differences in behavior before we merge it.

[Vaishnavi-Patil08]

Hi, I’d like to work on this. I’d like to take a closer look at the dual-stack behavior before implementing this. I’m planning to test the current/default 0.0.0.0 behavior against :: with IPV6_V6ONLY left entirely to the OS, including bindv6only=0 vs 1, IPv4/IPv6 connectivity and explicit bind values. I’ll use that to determine the smallest safe default change.