IPv6 Support

[Eleix]

It would be awesome to have native V6 support in the Synergy app. For networks where the focus is to be v6-only or v6-preferred it's impossible to use Synergy without configuring IPv4 at the current moment. In Synergy 2 you could specify the full IP address of the remote computer but I found it didn't matter if I used hostnames with only a AAAA record or tried to configure the address manually, both with and without brackets around the address and wasn't able to yield any results. The synergy server would immediately crash and restart repeatedly with the v6 address configured.

Additionally I feel IPv6 could provide for some unique synergy connections:

Link-Local only - Devices must be on the same LAN segment and can communicate with each other using their respective fe80 address.
Unique Local - Devices on different LAN segments with address space in the fd00::/8 space.
Unique Global - Devices are on completely different networks

With NAT64/DNS64 and 464XLAT it's possible to be connected to a LAN network that is entirely IPv6-only and still have access to legacy IPv4 Internet resources. Unfortunately this does not mean devices inside the LAN segment will have IPv4 addresses and would be nice to be able to continue to use Synergy in these kinds of environments.

 

[gb_lz]

I too tried ipv6, the server doesn't seem to bind to the ipv6 ip(s). I realize my use case is not very common but I have a network policy that when connected to a VPN, my local ipv4 traffic is being blocked leaving me with the option of using ipv6 or not being able to talk to local network. 

[phemale]

Synergy 3 is effectively unusable for most of my use cases, between the lack of IPv6 support, and heavy insistence on using mDNS for peer discovery (with the only manual option being entering an IPv4 address -- not all of the networks I use have IPv4).

At least with Synergy 1 I can tunnel the connections through SSH (over IPv6)...the newer version is a serious step backward.