My IPv6 changes have been merged a while ago. Nobody complained so far . There are still some things left to test. You can use the so-called link-local addresses, which are only valid in a network segment and are automatically set up by your operating system, they start with "fe80::". Localhost in IPv6 is "::1".
There are basically two things I'd like to have tested with different operating systems.
- Does the server show up with its link-local IPv6 address in the LANDiscovery, and are you able to connect to it? If not, can you connect with "--dest <ipv6-address>"?
- Does the name resolution with "--dest <hostname>" work correctly? This is trickier to test in its extents. Just let me list up some expected problems:
- The hostname does not resolve at all.
- The hostname resolves to IPv6 altough the system does not have a global IPv6 address configured.
- A dual-stack host gets resolved to its IPv4 address instead of its IPv6 adress, altough you have good global IPv6 connectivity.
- Resolving through MDNS aka Zeroconf/Bonjour/Avahi does not work.
Sadly IPv6 is completely disabled on the Tardis computers .