Opened 21 months ago

Last modified 9 months ago

#29113 new enhancement

Add IPv4/IPv6 connections to the heartbeat

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6, tor-relay, tor-dirauh
Cc: Actual Points:
Parent ID: Points: 2
Reviewer: Sponsor:

Description

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.

Child Tickets

TicketTypeStatusOwnerSummary
#28919defectclosedLog IPv4 and IPv6 connections in Tor's heartbeat message

Change History (1)

comment:1 Changed 9 months ago by teor

Parent ID: #24403

Belongs in a separate set of tickets

Note: See TracTickets for help on using tickets.