Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #4256

Closed (moved)
(moved)
Open
Created Oct 18, 2011 by Trac@tracbot

Hold high-uptime nodes to higher bandwidth standard

If http://torstatus.blutmagie.de/ is to be believed there are many, many nodes with effectively no bandwidth, some of which have long uptimes. I propose that nodes that fit this description be flagged as Invalid.

When you've been up for 6 months and have an Observed bandwidth of 0KB/sec there is a problem with your node. Maybe its mis-configured somehow, or the owner's ISP blocks Tor traffic, or a cosmic ray hit your cable modem. In any case, that node is not participating in the Tor network. See node "op56", flagged as Fast (!), for an example.

I suggest that minimum bandwidth requirements be tied to uptime duration. For example, a node that has been operating for a month must have at least 20KB of Observed bandwidth to be considered a valid node. This would allow nodes to demonstrate low-bandwidth while ramping up to their configured bandwidths, but prevent zombie nodes from falsely claiming to be capable of carrying Tor traffic.

Trac:
Username: tmpname0901

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