Tor Clients on IPv6

This is a top-level task that tracks the progress of IPv6 tor client support.

changed milestone to %Tor: unspecified

added component::core tor/tor ipv6 master-ticket milestone::Tor: unspecified points::(parent) priority::high severity::normal status::new tor-client type::task labels

Trac:
Priority: Medium to High

In #17840 (moved), tor clients bootstrap over IPv6 when configured to prefer IPv6, or only use IPv6. We also maintain bridge clients' preference for IPv6, while fixing some of their address selection code.

To prefer IPv6, a Tor client should set:

• ClientUseIPv4 0, or
• ClientUseIPv6 1 and ClientPreferIPv6[OR,Dir]Port 1, or
• configure bridges.

But this requires Tor users to know whether IPv4 or IPv6 works better for them, which is not ideal. In future releases, we could automatically use IPv6 if clients can bootstrap over it (#17217 (moved)), perhaps by using a "happy eyeballs"-like algorithm to try both IPv4 and IPv6, and switch between them depending on which one works better (#17835 (moved)).

Trac:
Milestone: Tor: 0.2.8.x-final to Tor: 0.2.9.x-final

This is a parent task; let's assign points to its subtasks only.

Trac:
Reviewer: N/A to N/A
Points: N/A to (parent)

This parent task doesn't have much in 0.2.9, and no-one plans on working on IPv6 support in 0.2.9.

Trac:
Milestone: Tor: 0.2.9.x-final to Tor: 0.2.???

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

Trac:
Username: rathann
Cc: N/A to dominik@greysector.net

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: ipv6 deleted, ipv6 tor-client master-ticket added

mentioned in issue #17812 (moved)

mentioned in issue #17813 (moved)

mentioned in issue #17817 (moved)

mentioned in issue #17834 (moved)

mentioned in issue #17854 (moved)

mentioned in issue #18051 (moved)

mentioned in issue #21310 (moved)

mentioned in issue #21311 (moved)

mentioned in issue #26664 (moved)

mentioned in issue #27753 (moved)

moved to tpo/core/tor#17811 (closed)

mentioned in issue tpo/community/relays-trac#27753 (closed)