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

Closed
Open
Opened Aug 10, 2011 by cypherpunks@cypherpunks

Add IPv6 support

At some point, IPv6 support should be added.

On the database level, this requires converting all given IPv4 INET values to IPv6 INET values, since IPv4 and IPv6 values do not play nicely together in PostgreSQL <= 8.4.8. (see: http://archives.postgresql.org/pgsql-admin/2011-07/msg00201.php) A helpful postgres dev suggests doing something along the lines of the following:

"address = '::ffff:0.0.0.0'::inet + (NEW.address::varchar::inet - '0.0.0.0'::inet)"

Next, statusapp.views.helpers.is_ipaddress and statusapp.views.helpers.is_ip_in_subnet should be rewritten to work with both IPv4 and IPv6 input and IP addresses.

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