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
  • #33248

Closed (moved)
Open
Opened Feb 11, 2020 by teor@teor

Prop 312: 3.5.5. Detailed Address Resolution Logs

This is an optional change, to help diagnose relay address resolution issues.

Relays (and bridges) should log the address chosen using each address resolution method, when:

  • address resolution succeeds,
  • address resolution fails,
  • reachability checks fail, or
  • publishing the descriptor fails. These logs should be rate-limited separately for successes and failures.

The logs should tell operators to set the Address torrc option for IPv4 and IPv6 (if available).

See proposal 312, section 3.5.5: https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-ipv6-addr.txt#n1083

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#33248