Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C Chutney
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 44
    • Issues 44
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • Chutney
  • Issues
  • #33229
Closed
Open
Created Feb 11, 2020 by teor@teor

Prop 311: 6.1. Test IPv6 ORPort Reachability on the Tor Network

Test the IPv6 ORPort Reachability and Extends changes in proposal 311, on the public tor network, with a small number of relays and bridges.

We can do public tests after each major feature is merged. We can also wait for multiple features to merge, and test them all.

Here are some useful features that we can test:

legacy/trac#33222 (moved) / legacy/trac#33226 (moved) IPv6 ORPort Reachability Self-Tests / Relay=3 Protocol legacy/trac#33223 (moved) Don't Publish Descriptor if IPv6 ORPort is Unreachable

See proposal 311, section 6.1, initial public test part: ​https://gitweb.torproject.org/torspec.git/tree/proposals/311-relay-ipv6-reachability.txt#n671

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