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

Closed (moved)
(moved)
Open
Created Aug 14, 2012 by Trac@tracbot

ORPort unreachable when setting OutboundBindAddress

Hi, I have a server running with 3 IP addresses, say A, B, C, on the same virtual adapter.

By default, all outbound connections are from IP A. I want Tor to be bound only to B, so I set the following directives:

OutboundBindAddress BDirListenAddress BORListenAddress B

The problem is that I get the following log entries, both for ORPort and DirPort

Aug 14 !01:36:04.409 [warn] Your server (A:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.

netstat correctly shows

#netstat -oanp | grep tortcp 0 0 !B:9030 0.0.0.0:* LISTEN 2567/tor off (0.00/0/0)tcp 0 0 !B:9001 0.0.0.0:* LISTEN 2567/tor off (0.00/0/0)tcp 0 0 !127.0.0.1:9100 0.0.0.0:* LISTEN 2567/tor off (0.00/0/0)

Other TCP entries correctly show that local endpoint is B

I believe it's a bug. I don't know Tor code but I believe that the code portion that ultimately logs the warning doesn't consider OutboundBindAddress when testing reachability. Disabling OutboundBindAddress and using A in other directives work fine.

Version 0.2.2.35 installed via YaST on openSUSE 11.4

Trac:
Username: lordyevon

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