Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #33252
Closed (moved) (moved)
Open
Issue 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:

#33246 (moved) Prop 312: 3.2.7. Automatically Enable an IPv6 ORPort #33238 (moved) Prop 312: 3.2.3. Use Local Interface IPv6 Address #33240 (moved) Prop 312: 3.2.4. Use Own Hostname IPv6 Addresses #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