Self-test reachability test - Listen address from ORPort is ignored, it uses default address unless specified via Address argument

Tor: 0.2.5.10 OS: Debian Wheezy 64 bit Installation: apt-get from deb.torproject.org

Configuration of server (one gigabit network card): em0: IP1 em0:0 IP2 em0:1 IP3 em0:2 IP4 em0:3 IP5

I tried to run multiple Tor instances to saturate the CPU of the server. I configured instances with different pid, datadirecotry and logfile as manual recommends, and specified the different IP as follows in each config file:

tor1.cfg ORPort IP1:port DirPort IP1:port OutboundBindAddress IP1

tor2.cfg ORPort IP2:port DirPort IP2:port OutboundBindAddress IP2

etc. so on

The first Tor instance started just fine, but the following ones didn't publish server descriptor because self reachability test did not pass. Why? They were all thinking they should be reachable on IP1 (def spend a huge amount of time on this.ault IP, em0 interface). Obviously that IP did not had the requried ports open for the additonal Tor instances so the test could not possibly pass.

Fix: I have added in each config file: Address IP1 Address IP2 and so on

After that it did the self reachability test on the correct IP address, and it passed of course, so server descriptor was published.

Tor should know to prase the IP address from ORPort and/or DirPort and make tests on that, obviously that's the address where the port should be open. Caution at -noadvertise and -nolisten options when this bug is inspected.