Bind to IPv6 addr.

[Leo-Besancon]

• document all added functions
• try in sandbox /simulation/labnet
• unit tests on the added/changed features
  • make tests compile
  • make tests pass
• add logs allowing easy debugging in case the changes caused problems
• if the API has changed, update the API specification

Only binding on IPv6 addresses (bind_private = "[::]:33034", bind_public = "[::]:33035" and bind_api = "[::]:33036") still works with IPv4 only interfaces.

Cf issue #2607

[Leo-Besancon]

Postman queries went through, however the current solution breaks the client.
I'll investigate more.

[sydhds]

Is this a good idea to make ipv6 the default? I'm wondering if it can confuse user. Maybe documentation about supported ip address (ipv4 + ipv6) can help?

[Leo-Besancon]

Is this a good idea to make ipv6 the default? I'm wondering if it can confuse user. Maybe documentation about supported ip address (ipv4 + ipv6) can help?

Oh, you mean a user that knows what 127.0.0.1 means but only sees ip = "::1" in the client config file, so he is lost?

Adding a comment above like the following would be good?

[default_node]
# Target IP of the API. Defaults to localhost, and works both with IPv4 and IPv6 interfaces.
ip = "::1"
private_port = 33034
public_port = 33035

[sydhds]

Is this a good idea to make ipv6 the default? I'm wondering if it can confuse user. Maybe documentation about supported ip address (ipv4 + ipv6) can help?

Oh, you mean a user that knows what 127.0.0.1 means but only sees ip = "::1" in the client config file, so he is lost?

Adding a comment above like the following would be good?

[default_node]
# Target IP of the API. Defaults to localhost, and works both with IPv4 and IPv6 interfaces.
ip = "::1"
private_port = 33034
public_port = 33035

I would even add something like:

... IPv4 (like 127.0.0.1) and IPv6 (like ::1) address.
I