Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #26094

Closed (moved)
Open
Opened May 13, 2018 by nusenu@nusenu

increase minimal bandwidth requirements, update the manpage, relay guide and FAQ

The man page has old minimal bandwidth requirements, let's update them to be consistent with the relay guide and the FAQ

man page currently says: https://www.torproject.org/docs/tor-manual-dev.html.en#BandwidthRate " If you want to run a relay in the public network, this needs to be at the very least 75 KBytes for a relay (that is, 600 kbits) or 50 KBytes for a bridge (400 kbits)  but of course, more is better; we recommend at least 250 KBytes (2 mbits) if possible. "

Proposed version for the man page: " If you want to run a relay in the public network, this needs to be at the very least 8 MBit/s (Mbps) for a relay or 1 MBit/s for a bridge   but of course, more is better; we recommend at least 16 MBit/s if possible. "

FAQ values: https://www.torproject.org/docs/faq.html.en#HowDoIDecide relay guide: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#BandwidthandConnections

context: https://lists.torproject.org/pipermail/tor-dev/2018-February/012916.html

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#26094