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 320
    • Issues 320
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 37
    • Merge requests 37
  • 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
  • #107
Closed
Open
Created Mar 11, 2005 by Trac@tracbot

Bandwidth reporting/bootstrapping

I've been running a Tor server (barf 0.0.9.5 Linux) for 3 weeks with very little usage. My reported bandwidth in the directory is pretty low, even if I have good connectivity (100 K/s). I have at most 1 or 2 connect attempt at the server port (9001) per day. DirPort is set to 0, since I do not want to mirror the directory. Knowing that Tor client picks node that display sufficient bandwidth, it looks like the server need to be 'bootstrapped' initially by forcing some traffic through it, with another Tor client with a EntryNodes and StrictEntryNodes set. There are several 0.0.9.5 servers in the directory with such low bandwidth.

[Automatically added by flyspray2trac: Operating System: Other Linux]

Trac:
Username: qbarf

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