Tor proxy does not work with IPv6 destination

[woodser]

Seems monero-wallet-rpc/cli does not work through Tor proxy to an IPv6 destination (IPv4 is ok).

Prerequisites:

• check ipv6 is supported with ping -6 feder8.me
• have tor daemon running

Tests:

1. start monero-wallet-rpc connecting to IPv4 node (node3.monerodevs.org:18089)
2. start monero-wallet-rpc connecting to IPv4 node (node3.monerodevs.org:18089) through SOCKS5 proxy
3. start monero-wallet-rpc connecting to IPv6 node (feder8.me:18089)
4. start monero-wallet-rpc connecting to IPv6 node (feder8.me:18089) through SOCKS5 proxy
5. start monero-wallet-rpc connecting to IPv6 node ([2a0b:f4c2:2:63]:18081)
6. start monero-wallet-rpc connecting to IPv6 node ([2a0b:f4c2:2:63]:18081) through SOCKS5 proxy

Tests 4 and 6 fail with the error message is "no_connection_to_daemon".

See original issue and comment from @fa2a5qj3: haveno-dex/haveno#1076 (comment)

[shortwavesurfer2009]

Did you change SOCKS5 proxy to [::1]:9050 or whatever? When tor starts it should open SOCKS5 proxies on both 127.0.0.1:9050 (v4 traffic) and [::1]:9050 (v6 traffic). Using 127.0.0.1 for v6 traffic will fail

[vtnerd]

Internally we use socks4 which only supports IPv4. So this will never work with IPv6 currently. I will put Socks5+IPv6 support in my next CCS proposal (hopefully I will have time for it).

[boldsuck]

Default system tor SocksPort 9050 & haveno's torrc SOCKSPort auto only listens on IPv4.
+ SocksPort [::1]:9050 or SocksPort [::1]:auto on IPv4 + IPv6

I don't know if SocksPolicy is useful if we have DisableNetwork 1 in haveno's torrc, but it doesn't hurt.

SocksPolicy accept 127.0.0.1
SocksPolicy accept6 [::1]
SocksPolicy reject *

[EDIT:]
Just for info: I tested Haveno with torrc settings:
SocksPort auto
SocksPort [::1]:auto

Then Haveno aborts starting. But this should be fixed now