IPv6 is not working when using SocksPort

Tor daemon replies to a SOCKS5 connect command with an IPv4 payload when using IPv6 thus making the client trying to receive too much bytes and failing to use IPv6 with a SOCKS5 connection.

I'll be submitting a patch for this soon. Just need to get this bug number and make the changes file.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information