Skip to content
GitLab
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
  • #5464
Closed (moved) (moved)
Open
Issue created Mar 24, 2012 by Mike Perry@mikeperryOwner

Decentralized measurement for network load balancing

EigenSpeed could provide a lot of security improvements to the Tor network in the face of all sorts of amplification attacks. It just sort of sucks because the passive version could not measure fast relays, and so we've never used it.

However, an active version based on CapProbe, PacketPair, etc could possibly measure capacity in as little as a handful of UDP packets, enabling distributed active lightweight measurements. We could also blend in circuit failure rate information.

As an alternative, we could also try using the passive EigenSpeed for slow relays and the bw authorities only for the faster ones...

The big problem is that this is basically a research effort. We're going to need to try at least a couple different versions of these designs and compare them to each other, and then compare them to the current bandwidth authorities, to make sure everything is as performant and abuse tolerant as possible.

Assignee
Assign to
Time tracking