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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed (moved)
Open
Opened Oct 18, 2005 by goodell@goodell

Path selection algorithm wastes exit bandwidth by choosing exits as relay nodes.

Nodes with more liberal exit policies should be chosen less frequently than nodes with more conservative exit policies, since they will naturally attract a disproportionate number of streams exiting to that port. For example, the fact that many streams traverse one particular node because it provides exit to port 6881 should not result in a concomitant bandwidth report that makes it more attractive to clients interested in exiting to port 80.

Ideally, we would (a) take into account that two hops of each circuit are chosen irrespectively of exit policy, and (b) we want to avoid "popular" nodes, where "popular" is some function of the scarcity of the ports to which they allow passage.

[Automatically added by flyspray2trac: Operating System: All]

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
0.1.2.x-final
Milestone
0.1.2.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#200