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
  • #20493

Closed
Open
Created Oct 28, 2016 by Tom Ritter@tom

Stem Documentation Wrong?

I'm going to try and copy but #20403 (moved) was the source of this.

On my relay (rittervg)'s consensus.routers['C0EDB08D7540D1DD3CA69809ED17D979F51B66E3'] ​https://atlas.torproject.org/#details/C0EDB08D7540D1DD3CA69809ED17D979F51B66E3 RouterStatusEntry:

  • .is_unmeasured is false
  • .measured is empty
  • .bandwidth is the value from the consensus w line (the agreed upon value by the bwauths)

If I manually pull all the server descriptors (which I'm trying to avoid but I guess I could) I get the following new values:

  • .observed_bandwidth - 1434333
  • .average_bandwidth - This is the value Atlas displays under 'Advertised Bandwidth'
  • .burst_bandwidth - 1536000

My relay's torrc says

  • RelayBandwidthRate 1250 KBytes
  • RelayBandwidthBurst 1500 KBytes

However stem describes these as:

  • https://stem.torproject.org/api/descriptor/router_status_entry.html :
  • bandwidth (int) -- bandwidth claimed by the relay (in kb/s)
  • measured (int) -- bandwidth measured to be available by the relay, this is a unit-less heuristic generated by the Bandwidth authoritites to weight relay selection
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking