Opened 8 days ago

#33224 assigned enhancement

Prop 311: 4.3.2. Add AssumeIPv6Reachable Option

Reported by: teor Owned by: teor
Priority: Medium Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6, prop311
Cc: Actual Points:
Parent ID: #33221 Points: 1
Reviewer: Sponsor: Sponsor55-must

Description

We add an AssumeIPv6Reachable torrc option and consensus parameter.

If IPv6 ORPort checks have bugs that impact the health of the network,
they can be disabled by setting AssumeIPv6Reachable=1 in the consensus
parameters.

If IPv6 ORPort checks have bugs that impact a particular relay (or bridge),
they can be disabled by setting "AssumeIPv6Reachable 1" in the relay's
torrc.

This option disables IPv6 ORPort reachability checks, so relays publish
their descriptors if their IPv4 ORPort reachability checks succeed.
(Unlike AssumeReachable, AssumeIPv6Reachable has no effect on the existing
dirauth IPv6 reachability checks, which connect directly to relay ORPorts.)

The default for the torrc option is "auto", which checks the consensus
parameter. If the consensus parameter is not set, the default is "0".

"AssumeReachable 1" overrides all values of "AssumeIPv6Reachable",
disabling both IPv4 and IPv6 ORPort reachability checks. Tor should warn if
AssumeReachable is 1, but AssumeIPv6Reachable is 0. (On directory
authorities, "AssumeReachable 1" also disables dirauth IPv4 and IPv6
reachability checks, which connect directly to relay ORPorts.
AssumeIPv6Reachable does not disable directory authority to relay IPv6
checks.)

See proposal 311, section 4.3.2:
https://gitweb.torproject.org/torspec.git/tree/proposals/311-relay-ipv6-reachability.txt#n403

Child Tickets

Change History (0)

Note: See TracTickets for help on using tickets.