On 22 Nov. 2016, at 02:26, Ralph Seichter tor-relays-ml@horus-it.de wrote:
On 21.11.2016 14:39, Tristan wrote:
IPV6 isn't backwards compatible, so literally every hop, skip, and jump on the Internet would need to be upgraded to support it. Many ISPs find it much easier and cheaper to just re-use the older IPV4 addresses.
IPv4 addresses are running out, and using IPv6 is not rocket science.
The IPv4 requirement on Tor relays exists to preserve Tor client anonymity.
Relays require an IPv4 address, because every relay in the Tor network needs to be able to connect to every other relay. If some relays can't reach other relays, then clients won't be able to select paths at random.
Finding a way around this restriction needs further research into anonymity in non-clique networks. This is the hard part of the problem.
The more customers actively ask for it, the more ISPs will comply. Mine certainly does, and I even choose ADSL routers accordingly. I configure all computers that are capable for IPv6, both servers and clients.
My Tor nodes are IPv6 capable, so if the Tor authors find a way to run Tor over IPv6, I will be happy to help with testing things. The necessary ports are already reachable.
Tor is IPv6 capable, and has been for years.
Relays (and bridges) that have both an IPv4 and IPv6 address can support dual-stack and IPv6-only clients.
Do you advertise an IPv6 ORPort on your relays and bridges?
Exits can support client access to dual-stack and IPv6-only websites.
Do you set IPv6Exit on your exits?
T