Opened 19 months ago

Last modified 6 days ago

#17811 new task

Tor Clients on IPv6

Reported by: teor Owned by:
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6 tor-client master-ticket
Cc: dominik@… Actual Points:
Parent ID: Points: (parent)
Reviewer: Sponsor:


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

Child Tickets

#4806Detect and warn when running IPv6-using client without IPv6 address privacy
#6772Fall back to alternative OR or Dir port if the current fails
#6939Missing IPv6 ORPort reachability check
#11360Listen on IPv6 by default for SocksPort *:Port
#17011chutney doesn't verify using IPv6 addresses
#17153tor test networks should allow IPv6 private addresses
#17217Change clients to automatically use IPv6 if they can bootstrap over it
#17327DirAuthority IPv6
#17573Update max_dl_per_request for IPv6 address length
#17774Update FallbackDir entry in man page for IPv6
#17782Relays may publish descriptors with incorrect IP address
#17813IPv6 address for urras
#17835Make ClientPreferIPv6ORPort/DirPort smarter
#17840Add a minimal implementation of ClientUseIPv4 so IPv6-only clients can bootstrapteor
#17845Add unit tests for IPv6 relay descriptors
#17849Warn if single-stack IPv4/IPv6 clients have very restricted guard choices
#17863Fixes to IPv6 address handling
#17889Make ClientPreferIPv6ORPort apply to bridge clients
#18051directory_send_command should decorate IPv6 addresses to avoid port ambiguitymalekbr

Change History (10)

comment:1 Changed 17 months ago by nickm

  • Priority changed from Medium to High

comment:2 Changed 17 months ago by teor

In #17840, 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), 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).

comment:3 Changed 17 months ago by teor

  • Milestone changed from Tor: 0.2.8.x-final to Tor: 0.2.9.x-final

comment:4 Changed 15 months ago by nickm

  • Points set to (parent)

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

comment:5 Changed 12 months ago by teor

  • Milestone changed from Tor: 0.2.9.x-final to Tor: 0.2.???

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

comment:6 Changed 8 months ago by teor

  • Milestone changed from Tor: 0.2.??? to Tor: 0.3.???

Milestone renamed

comment:7 Changed 6 months ago by nickm

  • Keywords tor-03-unspecified-201612 added
  • Milestone changed from Tor: 0.3.??? to Tor: unspecified

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

comment:8 Changed 6 months ago by rathann

  • Cc dominik@… added

comment:9 Changed 5 weeks ago by nickm

  • Keywords tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:10 Changed 6 days ago by nickm

  • Keywords tor-client master-ticket added
Note: See TracTickets for help on using tickets.