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 313
    • Issues 313
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 33
    • Merge requests 33
  • 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
  • #33252
Closed
Open
Created Feb 11, 2020 by teor@teor

Prop 312: 5.1. Test Relay IPv6 Addresses Discovery on the Tor Network

Test the IPv4 and IPv6 ORPort Address Detection changes in proposal 312, on the public tor network, with a small number of relays and bridges.

Here are some useful features that we can test:

legacy/trac#33246 (moved) Prop 312: 3.2.7. Automatically Enable an IPv6 ORPort legacy/trac#33238 (moved) Prop 312: 3.2.3. Use Local Interface IPv6 Address legacy/trac#33240 (moved) Prop 312: 3.2.4. Use Own Hostname IPv6 Addresses legacy/trac#33247 (moved) Prop 312: 3.2.7. Publish IPv4 Descriptor on Guessed IPv6 Reachability Failure

See proposal 312, section 5.1, initial public test part: https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-ipv6-addr.txt#n1461

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