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

Closed (moved)
Open
Opened Jan 25, 2012 by Karsten Loesing@karsten

Discuss shipping and enabling tor-fw-helper by default

We have a sponsor F deliverable for either July or November 2012 to "investigate NAT piercing approaches for relays and bridges."

Jake says that, in theory, we need to ship tor-fw-helper and actually enable it. That will fix 90% of the NAT issues that we have right away. It's been merged for a year but we're still not shipping it and enabling it by default. Steven just finished the Windows port of tor-fw-helper.

Does that mean we can now ship and enable it on all platforms in the next major Tor release, which is probably going to be 0.2.4.x?

If not, what's left to do? Or is it a bad idea for some reason?

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