Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 313
    • Issues 313
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #33247
Closed
Open
Created Feb 11, 2020 by teor@teor

Prop 312: 3.2.7. Publish IPv4 Descriptor on Guessed IPv6 Reachability Failure

Depends on disabling descriptor publication on reachability failures in legacy/trac#33223 (moved).

Should be done after the first IPv6 address guessing feature: legacy/trac#33238 (moved) or legacy/trac#33240 (moved).

If both reachability checks succeed, relays should publish their IPv4 and IPv6 ORPorts in their descriptor.

If only the IPv4 ORPort check succeeds, and the IPv6 address was guessed (rather than being explicitly configured), then relays should:

  • publish their IPv4 ORPort in their descriptor,
  • stop publishing their IPv6 ORPort in their descriptor, and
  • log a notice about the failed IPv6 ORPort reachability check.

See proposal 312, section 3.2.7, Guessed IPv6 Reachability Failure part: https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-ipv6-addr.txt#n567

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking