> On 9 Jan 2016, at 01:22, David Tomic <[email protected]> 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 > > <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
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ tor-relays mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
