Age | Commit message (Collapse) | Author |
|
We've talked about these, and in some cases begun to implement them.
|
|
Ignore create cells from clients when checking for relay reachability.
Part of 33222.
|
|
|
|
Part of 33222.
|
|
Update 4.2.3. Separate IPv4 and IPv6 Reachability Flags.
Add a detailed design for checking cells on reachability self-test
circuits.
|
|
Keep the monitoring summaries in proposals 311 and 312 in sync with
proposal 313.
Part of 33159.
|
|
Part of 33159.
|
|
Add an optional change that makes relays do bandwidth self-tests over
IPv6.
This change increases the connection and bandwidth IPv6 statistics.
Related to proposal 313, which covers IPv6 statistics.
Related to 33159.
|
|
When a change increases an IPv6 statistic, mention the impact in
proposals 311 and 312.
Related to proposal 313, which covers IPv6 statistics.
Part of 33159.
|
|
Part of 24404.
|
|
Part of 24404.
|
|
We want to allow relays to upgrade to trying both addresses in an
EXTEND2 cell, without requiring a new protocol version.
The spec documents the planned "choose at random" behaviour, but
allows relays to try both IPv4 and IPv6 in future.
Part of 24404.
|
|
Part of 24404.
|
|
We don't want to depend on extends preferring IPv4 or IPv6,
or the exact extend implementation, if we don't have to.
Part of 24404.
|
|
Part of 24404.
|
|
* don't ban useful behaviours, just mention that they might not happen
* don't talk about reachability, other tor instances don't care
* specify random choice between IPv4 and IPv6 (and add a TODO)
As suggested by Nick Mathewson.
Part of 24404.
|
|
As suggested by Nick Mathewson.
Part of 24404.
|
|
And add extra logging when tor would have previously found itself
reachable, but the new checks fail.
As suggested by Nick Mathewson.
Part of 24404.
|
|
Add an alternate design, suggested by Nick Mathewson.
Part of 24404.
|
|
As suggested by Nick Mathewson.
Part of 24404.
|
|
We want to support these two cases:
* upgrade to working IPv6,
* stay on IPv4-only, if a guessed IPv6 address isn't reachable.
Part of 24404.
|
|
Part of 24404.
|
|
Part of 24404.
|
|
Part of 24404.
|
|
Some of the statistics may also be available in relay heartbeat logs.
Part of 24404.
|
|
Improve the explanations of some of the references to proposal 306:
Client Auto IPv6 Connection. And add a section that specifically
mentions modifying that proposal.
Part of 24404.
|
|
Some IPv6 behaviour has changed in recent tor versions, as noted in the
proposal.
Part of 24404.
|
|
Where it's different from relay behaviour.
Part of ticket 24404.
|
|
And use short proposal names in references.
Part of 24404.
|
|
Related tickets: 24404 (proposal), 24403 (implementation).
|