Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #5143

Closed (moved)
(moved)
Open
Created Feb 15, 2012 by Trac@tracbot

ServerTransportPlugin sets or_port to '127.0.0.1:0'

When Tor is configured with

ORPort "[::]:9001" so on default linux it is configured to listen on both v4 and v6 sockets.

and obfsproxy configured to run in managed mode:

ServerTransportPlugin obfs2 exec /usr/local/bin/obfsproxy --log-min-severity=debug --no-safe-logging --logfile=/var/log/tor/obfsproxy.log --managed

we get:

Proxy environment: [...] or_port: '127.0.0.1:0' [...]

If we add a v4 only OrPort OrPort "0.0.0.0:9001" it works as expected:

[...] or_port: '127.0.0.1:9001' [...]

Trac:
Username: murble

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking