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

Closed (moved)
Open
Opened Nov 24, 2011 by Karsten Loesing@karsten

Extend Tor to no longer assume that a relay or bridge has exactly one address

We should extend Tor to no longer assume that a relay or bridge has exactly one address. This probably means implementing proposal 186, but maybe it means more than that. We should make sure that all places in Tor use a list of addresses per relay or bridge. This gets tricky when we want to connect to a relay or bridge; do we try all addresses at once? or just one? or do we fall back to the next if the first fails?

The code changes are part of the March 31, 2012 deliverable for sponsor G. Merging code into master is sufficient here, no (alpha) releases or bundles involved.

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