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

Closed (moved)
Open
Opened Sep 24, 2015 by starlight@starlight

long-running client path-selection not seeing some (fast) exit nodes

I noticed that a couple of fast new exit relays were never being chosen, which is strange because with an exit probability of over 1% that should happen once in awhile.

Then used setconf ExitNodes= to force one of them and the client balked, saying

All routers are down or won't exit -- choosing a doomed exit at random.
No specified exit routers seem to be running: can't choose an exit.
Failed to choose an exit server

Then restarted the client and it worked.

Client was running uninterrupted for 10 days when this occurred.

torrc specifies UseMicrodescriptors 0 (due to various other misbehaviors related to running with micro-descriptors enabled.

This appears to be an area in need of QA work.

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#17147