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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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
  • #29113

Closed (moved)
Open
Opened Jan 18, 2019 by teor@teor

Add IPv4/IPv6 connections to the heartbeat

When we implement IPv6 extends, we'll need to monitor how many IPv4 and IPv6 connections a relay is making, using every combination of:

  • IPv4/IPv6
  • initiate/accept

We may also want to add the reason that the connection was initiated:

  • IPv4/IPv6
  • reachability (origin, authorities only) / client (origin, authorities and relay also act as clients) / extend (relays and authorities only)

It's probably safe to also count all reachability circuits, but it might not be safe to count client circuits on clients, or extend circuits. Let's think about the privacy implications before adding these to the heartbeat.

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