Opened 5 years ago

Closed 4 years ago

Last modified 4 years ago

#15235 closed task (fixed)

Identify the state of IPv6 support in Tor

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: 0.2.8.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-client, tor-relay, ipv6, research, 027-triaged-1-out
Cc: Actual Points:
Parent ID: Points: medium
Reviewer: Sponsor:

Description

What works for IPv6 today? What doesn't? What's hard to configure?

  • Can clients use ipv6 to connect to Tor?
  • Can clients resolve Ipv6 addresses with Tor?
  • Does automapping to ipv6 addresses work?
  • Can we exit to ipv6?
  • Can bridges be IPv6-only? (no, I don't think so)
  • Can relays be IPv6 only? (no)

And many more.

We should ideally not only hand-check tehse issues, but write tests for some of them.

Child Tickets

Change History (10)

comment:1 Changed 5 years ago by nickm

Status: newassigned

comment:2 Changed 5 years ago by nickm

Keywords: 027-triaged-1-out added

Marking triaged-out items from first round of 0.2.7 triage.

comment:3 Changed 5 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.???

Make all non-needs_review, non-needs_revision, 027-triaged-1-out items belong to 0.2.???

comment:4 Changed 4 years ago by nickm

Milestone: Tor: 0.2.???Tor: 0.2.8.x-final

comment:5 Changed 4 years ago by nickm

Points: medium

comment:6 Changed 4 years ago by teor

Severity: Normal

The current state of IPv6 for clients is:

  • 5 directory authorities have IPv6 addresses
    • these addresses aren't hardcoded into tor, nor would they be parsed if they were (#17327)
  • Tor doesn't know how to tell if IPv6 works, so it just uses IPv4 by default (#17217)
  • Tor doesn't have a setting to disable IPv4 (#9068)
  • Tor won't bootstrap over IPv6 (#17281)
  • Tor doesn't listen on IPv6 by default on the SOCKSPort (#11360)

(#6027 used to be about IPv6 on authorities, but we closed it because it was duplicated by a lot of other tickets and existing code.)

comment:7 in reply to:  6 Changed 4 years ago by teor

Replying to teor:

5 directory authorities have IPv6 addresses
these addresses aren't hardcoded into tor, nor would they be parsed if they were (#17327)

Fixed, awaiting #17813 to see if urras has an IPv6 address in its new config. (Because of this, 4 directory authorities now have IPv6 addresses hard-coded into tor.)

Tor doesn't know how to tell if IPv6 works, so it just uses IPv4 by default (#17217)

Tor still needs to be configured manually for IPv6. We probably want to keep it this way until we have more relays on IPv6 for anonymity and load-balancing reasons.

Tor doesn't have a setting to disable IPv4 (#9068)

Fixed in #17840

Tor won't bootstrap over IPv6 (#17281)

Fixed in #17840

Tor doesn't listen on IPv6 by default on the SOCKSPort (#11360)

But it can be configured with an explicit IPv6 SOCKSPort.

New items:

  • We're running an opt-in trial for fallback directories (#17158), about 20% of them have IPv6 addresses (#8374). This reduces client dependence on the IPv6 authorities.

comment:8 Changed 4 years ago by teor

As of #17840, clients can bootstrap by setting:

  • ClientUseIPv4 0 (IPv6-only) or
  • ClientUseIPv6 1 and ClientPreferIPv6DirPort 1 and ClientPreferIPv6ORPort 1 (dual-stack).

In addition to the 4 authorities on IPv6, clients on IPv6 will use the 20% of fallback directories with IPv6 addresses to bootstrap.

comment:9 Changed 4 years ago by nickm

Resolution: fixed
Status: assignedclosed

I believe we can call this "fixed" then?

Please reopen if not.

comment:10 Changed 4 years ago by teor

I've been keeping the IPv6 Roadmap up to date. It's the best source for IPv6 progress, since we've closed this ticket.
https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/IPv6

Note: See TracTickets for help on using tickets.