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 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • 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
  • #1992

Closed
Open
Created Oct 01, 2010 by Roger Dingledine@armaReporter

relays resolve hostname every time they compute dir fetch schedule; but bridges resolve too seldom

directory_fetches_from_authorities() calls router_pick_published_address() whenever server_mode(options) is true.

This happens during directory_get_from_dirserver(), directory_command_should_use_begindir(), dir_routerdesc_download_failed(), directory_info_has_arrived(), update_consensus_networkstatus_fetch_time(), launch_router_descriptor_downloads(), update_router_descriptor_downloads(), etc.

Sounds like we should refactor things so it writes its guessed address to a variable and just reads that variable, and then have a periodic event (scheduled when we want it, rather than scheduled by accident because we think about doing a directory fetch) that writes an address into the variable.

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