[tor-relays] Why is Tor trying to check the wrong ORPort/DirPort addresses?

[s7r]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello,

I have experienced exactly the same problem with similar networking
configuration and reported it here:

https://trac.torproject.org/projects/tor/ticket/13953

It's being worked on.

In your case, however, it appears that the Address argument isn't
working and we need to find out why. I only want to highlight not to
confuse Address with OutboundBindAddress which are separate things and
both needed. The only difference in your setup vs mine is the Debian
version (you are on Jessie, I was on Wheezy). Please retry with these
lines in the config:

ORPort 50.7.178.99:444
DirPort 50.7.178.99:83
OutboundBindAddress 50.7.178.99
Address 50.7.178.99
RunAsDaemon 1
[add your other required config lines such as Log notice file and
DataDirectory]

Do this for every instance and substitute the IP address and ports per
each one. After you make sure the configuration files for all your Tor
instances contain the above data do what teor asked and provide the
relevant section of the debug log.

On 1/9/2016 12:42 AM, Tim Wilson-Brown - teor wrote:
> 
>> On 9 Jan 2016, at 01:22, David Tomic <david at tomic.com.au 
>> <mailto:david at tomic.com.au>> wrote:
>> 
>> I got a little bit excited a few minutes ago when I discovered
>> https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-create.8.txt
>>
>>
>> 
However, that doesn't appear to have made any difference either.  For
>> some reason the reachability tests are still insisting on trying
>> to connect to .102.
> 
> Tor should only fall back to using an interface address when it
> fails to parse the Address torrc option. So you may have found a
> bug in the tor function resolve_my_address(). (Tor should also
> probably pay attention to the address in the ORPort line when
> testing reachability, but that's a separate issue.)
> 
> Can you please choose a tor instance with this issue, and provide: 
> * The exact Address, ORPort and DirPort lines (or the entire torrc,
> if you're able) * The debug-level log output for the first and
> second calls to resolve_my_address() * there will be a lot of
> output here, and it can reveal sensitive info - don't leave debug
> logging on all the time!
> 
> Tim
> 
> Tim Wilson-Brown (teor)
> 
> teor2345 at gmail dot com PGP 968F094B
> 
> teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F
> B5A9D14F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBCAAGBQJWkE8uAAoJEIN/pSyBJlsR54oH/2UqOIL4UugD5024s9q1ZEw4
lp+K8c3vGcgLgI/l2Nm0hI95X1RwX6+bNjmtVpw1oC9Cc4wIM21ngrU9kRiveLZc
scoYj+N8bBoyMTpXG01mWEKT/4H5rmvOYdoxYlL5+7tMtGdjGKJ3BigZSk2+D8n+
b1Z5zszr2WElGIF9WNoJCD8iFqCLGUDSCHB0ZJ/+tPqKYqy4ffQT4dyQjscqh26u
6KwxrdnU4GkOYjtW5QYK1LoIvvwVKjjLUSNlTb3D9P6IljzQVfhcDkLw8j0Ksl4r
bwG4dfgZ84dteXfK15hGmqidVAC1hJm4+zxRGJ+FrRT7S9k66r7u8Wl0zfw9Fek=
=G5K3
-----END PGP SIGNATURE-----