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

Closed (moved)
Open
Opened Oct 27, 2017 by Roger Dingledine@arma

exitaddresses, and bulkexitlist, (and check?), don't know about IPv6

https://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=69.55.226.35&port=80 gives me a pile of ipv4 addresses. I think it parses https://check.torproject.org/exit-addresses plus maybe descriptors or consensuses to get exit policies.

But tordnsel was written back when IPv6 was not a thing. So that means every step of our pathway is missing the concept of IPv6.

I guess the most urgent part to fix, which ties into metrics, is that we aren't collecting the ipv6 exit addresses of relays, which means we won't be able to look back in time and answer questions that have to do with ipv6 connections out of Tor.

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