[tor-bugs] #10519 [Tor]: tor uses default IP for dirport instead of the one defined in DirPort

[Tor Bug Tracker & Wiki]

#10519: tor uses default IP for dirport instead of  the one defined in DirPort
-------------------------+------------------------------
     Reporter:  torland  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  Tor: unspecified
    Component:  Tor      |    Version:  Tor: 0.2.4.18-rc
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+------------------------------

Comment (by Pascal):

 This bug is actually a bit worse than the original description would make
 it appear.  This problem actually applies to ORPort as well as DirPort (in
 0.2.4.22 at least) and depending upon what is running on the default IP
 can make you think your relay is working correctly even when it is not.  A
 config containing:

 ORPort a.b.c.33:443
 OutboundBindAddress a.b.c.33

 but no Address will get:

 [notice] Now checking whether ORPort a.b.c.d:443 is reachable... (this may
 take up to 20 minutes -- look for log messages indicating success)

 where a.b.c.d is the default IP.  Depending upon what else is running on
 the box you will then get one of:

 [warn] Your server (a.b.c.d:443) has not managed to confirm that its
 ORPort is reachable. Please check your firewalls, ports, address,
 /etc/hosts file, etc.
 [notice] Self-testing indicates your ORPort is reachable from the outside.
 Excellent. Publishing server descriptor.

 but either way the relay will not actually show up in the directory.
 Again, even though it says "Publishing server descriptor", if Address is
 not set and ORPort is not the default IP then the relay will not actually
 get published.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10519#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online