Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #33159

Closed (moved)
Open
Opened Feb 05, 2020 by teor@teor

Write a proposal for monitoring IPv6

For sponsor 55, I need to write a proposal that covers these objectives:

  • O1.4 - Measure the number of Tor relays that support IPv6 reachability checks (#33051 (moved))
  • O1.5 - Measure the number of connections, and consumed bandwidth, using IPv4 and IPv6 (#33052 (moved))

My current thinking is that:

  • tor should log the number and consensus weight of relays that support IPv6 reachability checks, because we will need those numbers during testing
  • these numbers are available in the consensus

Here's what the proposal requires:

  • calculate relay IPv6 reachability numbers a few times during the project (we may as well use the tor logs)
  • collect IPv6 connection and bandwidth statistics on tor relays
  • calculate the IPv6 connection and bandwidth amounts a few times during the project

Here are some other useful things we might do:

  • split the collected IPv6 statistics by client/relay
  • calculate the guard-but-not-exit relays that support IPv6 client connections
  • log IPv6 statistics in tor's heartbeat logs (we can't use these logs for our project reports, because they only show the local relay's statistics)
  • calculate IPv6 reachability relay count and consensus weight on consensus-health
  • add a pseudo-flag for relay IPv6 reachability support in Relay Search
  • add metrics graphs that shows our progress on
    • IPv6 reachability
    • client IPv6 support on relays
    • IPv6 connections and bandwidth

We definitely won't have time to do all of these optional things, so we should priorise, once the essential work is done.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.4.4.x-final
Milestone
Tor: 0.4.4.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#33159