Skip to content

GitLab

  • Menu
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 832
    • Issues 832
    • 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
  • #6489

Closed
Open
Created Jul 30, 2012 by proper@proper

Document that clients also have BWRate and BWBurst.

The manual only talks about limiting bandwidth for relays.

Tor clients, especially hidden servers do not have an option to limit bandwidth or traffic. I am suggesting that feature.

Use cases:

  • Tor user, especially hidden servers want to reserve some free non-Tor bandwidth for other things (software downloads, updates, non-Tor browsing, etc.).
  • Tor user has a limited amount of traffic available in it's plan.
  • DDoS protection.
  • Workaround for legacy/trac#6473 (moved). (bandwidth related anonymity set reduction)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking