Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 329
    • Issues 329
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #40471
Closed
Open
Issue created Sep 16, 2021 by Roger Dingledine@armaReporter

Don't give weights to v3 dir auths

In the old Torflow, we had a little check that decided not to include opinions about the main network dir auths. That way they remain unmeasured, so they don't attract much network load from clients.

That check doesn't seem to have been done in sbws. So now that we have four bwauths running swbws, moria1 is now getting more traffic that isn't dir auth related: https://metrics.torproject.org/rs.html#details/9695DFC35FFEB861329B9F1AB04C46397020CE31

We could fix this in sbws, to check if the relay has the Authority flag and not write out a line for it.

Or we could fix this on the Tor side (cc @dgoulet), where Tor decides that a bwauth line for an Authority relay should be skipped.

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