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

Closed (moved)
Open
Opened Sep 14, 2015 by teor@teor

Do we need ExitPolicy private[4|6]:... ?

In #16069 (moved), we changed accept6/reject6 ... so they only produced IPv6 rules. But this doesn't apply to accept6/reject6 private:... , which still produces both IPv4 and IPv6 rules.

#16069 (moved) added a warning on accept6/reject6 private, infoming the user they're gettingn IPv4 and IPv6 rules.

Do we need a private4 or private6 alias for IPv4 and IPv6 private addresses, respectively? Does anyone want to specify treatment of IPv4 and IPv6 private addresses separately?

A workaround is to use a policy like:

accept *4:*
reject private:*
accept *6:*

Or to specify each private address range and local server address separately.

To upload designs, you'll need to enable LFS and have 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#17056