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 831
    • Issues 831
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • 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
  • #1075

Closed
Open
Created Aug 29, 2009 by Roger Dingledine@armaReporter

reachability controller status events too liberal

edmanm:#vidalia arma: so i guess tor throws a REACHABILITY_FAILED event for +every testing circuit that fails (but not necessarily a CHECKING_REACHABILITY +event for every testing circuit it launches). edmanm:#vidalia is there a particular threshold of failures at which tor +decides "ok, i'm really not reachable. user needs to fix his network."? edmanm:#vidalia or if i wait long enough will i finally get a +REACHABILITY_FAILED event with an ERR severity?

[Automatically added by flyspray2trac: Operating System: All]

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