Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T torflow
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • torflow
  • Issues
  • #6131

Closed
Open
Created Jun 11, 2012 by Roger Dingledine@armaOwner

bwauths learn to recognize Unmeasured=1 in consensus line and treat it differently

In legacy/trac#2286 (moved) we're going to change directory authorities to say something like "w Bandwidth=100 Capped=1" for relays that don't have enough Measured lines.

Torflow's BWAuthority needs to learn not to get snookered by the 100 into thinking that the relay's peers are all the other "Bandwidth=100" relays.

Assignee
Assign to
Time tracking