Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • 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
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

Admin message

GitLab has been upgraded GitLab 16, please report any issues!

  • Legacy
  • TracTrac
  • Issues
  • #3282
Closed
Open
Issue created May 24, 2011 by Karsten Loesing@karsten

Extend the new Python Torperf to talk to tor's control port

After finishing #3281 (closed), we should extend Torperf to talk to the control ports of the tor processes it started before. Torperf should use TorCtl for this task similar to extra_stats.py and entrycons.py. In fact, we can probably re-use most of the code from these two files.

Connecting to tor's control port has two purposes that have to be performed by the new Torperf: First, Torperf may have to influence tor's guard node selection algorithm depending on its configuration, and second, Torperf will have to process control port events and write them to a local .extradata file.

Assigning to tomb upon request.

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