Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,066
    • Issues 1,066
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

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.

  • The Tor Project
  • Core
  • Tor
  • Issues
  • #2178

Closed
Open
Opened Nov 11, 2010 by Nick Mathewson@nickm🐭Owner

We launch dummy descriptor fetches more often than needed

Right now, we have code in update_router_descriptor_downloads() to launch a fetch for authority.z if we want to learn our IP from a directory fetch. We do this if:

  • We're a server
  • We don't have the Address option set
  • At least 20 minutes have passed since we last launched a router descriptor download
  • At least 20 minutes have passed since we last launched a

Per discussion in bug legacy/trac#652 (moved), we could be even more quiet about launching these fetches. We could also require that

  • At least 20 minutes have passed since we last launched any appropriate directory op.
  • At least 20 minutes have passed since we got a new incoming connection on what we think our IP is.
  • At least 20 minutes have passed since we got confirmation of our current IP in a NETINFO cell

We could also make the "20 minutes" value configurable by a networkstatus parameter.

This is a minor issue, since the current behavior is inelegant, but not actually hurting anything.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.4.5.x-freeze
Milestone
Tor: 0.4.5.x-freeze (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/core/tor#2178