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

Closed (moved)
Open
Opened Aug 19, 2011 by Jacob Appelbaum@ioerror

Allow Tor to listen on a specific interface for ORPort

I have a use case where my Tor has a dynamic IP on one interface and only one interface. The device in question has three interfaces and two of them should will not offer an ORPort.

It is possible to offer specific Tor services by interface only if the interface has a static ip. This means that I have to hard code ip addresses into my torrc and this doesn't scale very well. It would be nice to listen on whatever ip address is bound to a given interface. Here is an example stanza:

  ORPort eth0:auto by-interface

It would also be nice if it was possible to do this for other things like the TransPort, etc.

Any thoughts on this would be most appreciated.

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