Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #4484

Closed (moved)
(moved)
Open
Created Nov 16, 2011 by Roger Dingledine@arma

parameterize bandwidth cutoffs for Guard and Fast flags

Right now we guarantee the Fast flag to any node with (a hard-coded) 20KB of bandwidth, and guarantee the Guard flag to any node with (also hard-coded) 250KB of bandwidth.

We should turn those into parameters, since the nice people doing Tor network simulations don't want to hack our code between sims when comparing values. We should do it in 0.2.2 so they can do simulations on stable Tor too.

(In a later ticket I'm going to suggest that 20KB has become a dumb value for AuthDirFastGuarantee, but that's a bug, not this feature.)

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