Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 342
    • Issues 342
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 35
    • Merge requests 35
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • 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
  • #23592
Closed
Open
Issue created Sep 20, 2017 by teor@teor

Update longclaw's IPv4 address (after it moves)

Longclaw will soon move IPv4 addresses. Its current address was added in 0.2.6.2-alpha.

Will it have multiple IPv4 addresses? (One for the hard-coded address, and one for the consensus?)

How does this impact 0.2.5 clients?

  • Clients with a consensus will use whatever address longclaw signs in its relay descriptor
  • Clients without a consensus:
    • 0.2.8 and later try multiple authorities without waiting for failures, so they will be fine
    • 0.2.4, 0.2.6, and 0.2.7 are no longer supported: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking