Make IPv6-only clients work and bootstrap

We have a big pile of IPv6 tickets, but none of them actually is for this.

If you start a tor client on an IPv6-only connection, it should bootstrap and connect to the network happily.

Part of this can be solved through the use of fallback directories on ipv6, but we need to make sure that the code actually works (#15235 (moved))

changed milestone to %Tor: 0.2.8.x-final

added 028-triage component::core tor/tor ipv6 milestone::Tor: 0.2.8.x-final owner::teor parent::17840 points::medium/large priority::high resolution::fixed severity::normal status::closed type::defect labels

The IPv6 code for fallback directory (and authority) line parsing doesn't work, even for clients. I was working on it in #6027 (moved) & #8374 (moved), I'll make future comments here.

Trac:
Cc: ln5 to ln5, mcs
Severity: N/A to Normal

Trac:
Parent: N/A to #17811 (moved)

Design notes:

• Add ClientPreferIPv6DirPort to break ties for directory documents on IPv4 / IPv6 systems.

Replying to teor:

Design notes:

• Add ClientPreferIPv6DirPort to break ties for directory documents on IPv4 / IPv6 systems.

See #17834 (moved)

I wonder how much of this works already?

Clearly, we need at least some authorities or fallback directories with hard-coded IPv6 addresses (#17327 (moved)), otherwise an IPv6-only client has no hope of bootstrapping.

I'm not sure if we need to fix reachable addresses (#9067 (moved)), unless it denies all IPv6 directory or OR addresses by default (#9068 (moved)).

I'm not sure if clients already use whatever addresses they can bootstrap and OR over (#17217 (moved)), or if they always choose IPv4 addresses. Will I need to set ClientPreferIPv6ORPort or ClientPreferIPv6DirPort (#17834 (moved))?

I suspect that if we don't listen on IPv6 by default on the SOCKSPort (#11360 (moved)), then this will be a show-stopper, but only after the client is connected to the Tor network.

I'll be doing my testing with a client build with:

• The latest patch for authority IPv6 addresses (#17327 (moved))
• ClientIPv6 1 set

Trac:
Status: new to accepted
Owner: N/A to teor

The changes in #17840 (moved) are enough to get clients on IPv6 bootstrapping and connecting, when configured correctly, although quite a few improvements could be made (see my comments in #17840 (moved), and the list of tasks in #17811 (moved)).

This ticket can close when #17840 (moved) merges.

Trac:
Parent: #17811 (moved) to #17840 (moved)

We resolved this in #17840 (moved) by introducing ClientUseIPv4. IPv6-only clients should set ClientUseIPv4 to 0.

They then bootstrap using IPv6 authorities or fallback directory mirrors (#17158 (moved)), and connect using IPv6 relays.

See my branch feature17840-v11-squashed in #17840 (moved).

Trac:
Resolution: N/A to fixed
Status: accepted to closed

closed

mentioned in issue #17327 (moved)

mentioned in issue #17376 (moved)

mentioned in issue #17573 (moved)

mentioned in issue #17812 (moved)

mentioned in issue #17813 (moved)

mentioned in issue #24322 (moved)

mentioned in issue tpo/core/chutney#17812 (closed)

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

mentioned in issue tpo/core/tor#24322 (closed)

mentioned in issue tpo/core/dirauth#17813 (closed)