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

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

Prop 313: 4. Collect IPv6 Bandwidth Stats on Relays and Bridges

We propose that relays (and bridges) collect IPv6 consumed bandwidth statistics.

To minimise development and testing effort, we propose re-using the existing "bw_array" code in rephist.c.

(We might want to move this code into separate relay-only code and header files, because it is relay-specific.)

In particular, tor currently counts these bandwidth statistics:

  • read,
  • write,
  • dir_read, and
  • dir_write.

We propose adding the following bandwidth statistics:

  • ipv6_read, and
  • ipv6_write. (The IPv4 statistics can be calculated by subtracting the IPv6 statistics from the existing total consumed bandwidth statistics.)

We believe that collecting IPv6 consumed bandwidth statistics is about as safe as the existing IPv4+IPv6 total consumed bandwidth statistics.

See proposal 313, section 4: https://gitweb.torproject.org/torspec.git/tree/proposals/313-relay-ipv6-stats.txt#n118

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#33263