Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #33247

Closed (moved)
Open
Opened 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 #33223 (moved).

Should be done after the first IPv6 address guessing feature: #33238 (moved) or #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 admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#33247