Warn if single-stack IPv4/IPv6 clients have very restricted guard choices

Yawning: The futueproof thing would be to warn if the selected protocol limits the number of guards to < N% probably? Using what a dual stack host can reach as the baseline.

changed milestone to %Tor: 0.3.0.x-final

added actualpoints::0 component::core tor/tor easy ipv6 isaremoved milestone::Tor: 0.3.0.x-final parent::17811 points::3 priority::medium prop259 resolution::fixed severity::normal status::closed tor-03-unspecified-201612 tor-guard type::enhancement labels

It's worth noting that the code to allow IPv6 guards was introduced in a previous tor version.

Trac:
Description: ``` Yawning: The futueproof thing would be to warn if the selected protocol limits the number of guards to < N% probably? Using what a dual stack host can reach as the baseline.

**to**

 Yawning: The futueproof thing would be to warn if the selected protocol limits the number of guards to < N% probably?
Using what a dual stack host can reach as the baseline.

We don't currently warn if FascistFirewall is set, even though that restricts guard choices.

If we do implement this, the warning should apply to:

• IPv6-only clients
• Clients that set any of the ReachableAddresses options
• Clients that set any of the ExcludeNodes or Nodes options (???)
• IPv4-only clients (for future-proofing)

It could be easier to implement this after #9068 (moved) is done.

We can use the current proportion of relays on IPv4 ORPort 443 / DirPort 80 as a guide - these relays are accessible from clients with FascistFirewall set.

I think we can defer this, because IPv6 client support is experimental, and requires explicit user action to enable. But I'd happily review a patch for it, or write one if I had the time.

It will be easy to write a patch for this once #17840 (moved) is merged.

Trac:
Keywords: N/A deleted, easy added

Trac:
Points: N/A to medium

Throw most 0.2.8 "NEW" tickets into 0.2.9. I expect that many of them will subsequently get triaged out.

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

These are also prop259-related

Trac:
Keywords: N/A deleted, prop259 added

Trac:
Keywords: N/A deleted, tor-guard added

Trac:
Points: medium to 3

Trac:
Keywords: N/A deleted, isaremoved added
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:
Milestone: Tor: 0.3.??? to Tor: unspecified
Keywords: N/A deleted, tor-03-unspecified-201612 added

This was implemented as part of proposal 217 in #19877 (moved).

Trac:
Actualpoints: N/A to 0
Reviewer: N/A to N/A
Status: new to closed
Milestone: Tor: unspecified to Tor: 0.3.0.x-final
Resolution: N/A to fixed

closed

changed time estimate to 24h

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