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 318
    • Issues 318
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • 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
  • #30955
Closed
Open
Created Jun 24, 2019 by teor@teor

Update the fallback entry in the man page

"FallbackDir ipv4address:port" "FallbackDir ipv4address:dirport"

"DirAuthority [nickname] [flags] ipv4address:port" "DirAuthority [nickname] [flags] ipv4address:dirport"

And similarly for orport.

"The provided port value is a dirport; clients ignore this in favor of the specified "orport=" value." "Clients always use the orport. Relays prefer the dirport, but will use the orport in some circumstances."

Add something to the FallbackDir entry talking about how the DirPort is used by the checking script?

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