Improve documentation around IPv4/IPv6 address binding

[greatest-ape]

No description provided.

[alopatindev]

Thanks. However this documentation doesn't explain how to bind on both IPv4 and IPv6 loopback interfaces (not wildcard addresses).

[greatest-ape]

It does, though? ::1 will bind on loopback on both IPv4 and IPv6 on Linux, if I’m not mistaken.

[alopatindev]

Oh, got it. Well it doesn't work to me on GNU/Linux: with address = "[::1]:3000" and only_ipv6 = false it binds to IPv6 [::1]:3000, not IPv4 127.0.0.1:3000.

It works with [::ffff:127.0.0.1]:3000 though: it binds to IPv6 [::ffff:127.0.0.1]:3000 and to IPv4 127.0.0.1:3000.

[greatest-ape]

Hmm, I was mistaken. However, [::ffff:127.0.0.1]:3000 won't actually be able receive IPv6 traffic in my testing. This seems to chime with https://serverfault.com/a/1102261 . Did you get it to work? That is, with the current code, only [::] works for receiving both IPv4 and IPv6 traffic. I've updated the docs to reflect this (#219), but ideally, aquatic should be rewritten to be able to open one socket for IPv4 and another for IPv6..

[alopatindev]

Did you get it to work?

Hm, I rechecked. Turns out it's true: I wasn't able to receive IPv6 packets on the [::ffff:127.0.0.1]:3000 :(

ideally, aquatic should be rewritten to be able to open one socket for IPv4 and another for IPv6

Yeah, I totally agree.

[greatest-ape]

Did you get it to work?

Hm, I rechecked. Turns out it's true: I wasn't able to receive IPv6 packets on the [::ffff:127.0.0.1]:3000 :(

ideally, aquatic should be rewritten to be able to open one socket for IPv4 and another for IPv6

Yeah, I totally agree.

Ok! Anyway, thanks for bringing it to my attention.