<div dir="ltr"><div dir="ltr" style="font-size:12.8px">I got a little bit excited a few minutes ago when I discovered <a href="https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-create.8.txt" target="_blank">https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-create.8.txt</a><div><br></div><div>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.</div></div><div class="" style="font-size:12.8px"></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 9 January 2016 at 00:39, Roman Mamedov <span dir="ltr"><<a href="mailto:rm@romanrm.net" target="_blank">rm@romanrm.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, 8 Jan 2016 23:39:59 +1100<br>
David Tomic <<a href="mailto:david@tomic.com.au">david@tomic.com.au</a>> wrote:<br>
<br>
</span><span class="">> The problem appears when Tor tries to verify that my ORPort/DirPort are<br>
> reachable, because for some reason it's trying to check the wrong IP<br>
> address?<br>
<br>
</span>Did you try setting OutboundBindAddress?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
With respect,<br>
Roman<br>
</font></span></blockquote></div><br></div>