<div dir="ltr">I have already done that, so that doesn't appear to be the problem. I see exactly the same problem even when I'm only starting up a single instance. Tor binds everything to the correct ip:port, but the reachability test always tries to connect to the .102 ip address.<div><br></div><div>Is it possibly something to do with the way that my network interfaces are configured? FWIW I haven't actually touched anything there, it's still exactly how it was originally provided to me by the host:</div><div><br></div><div><div># cat /etc/network/interfaces</div><div># Automatically generated by OnApp (2.3.3)</div><div>auto lo</div><div>iface lo inet loopback</div><div><br></div><div>auto eth0</div><div>iface eth0 inet static</div><div><span class="" style="white-space:pre"> </span>address 50.7.178.98</div><div><span class="" style="white-space:pre"> </span>netmask 255.255.255.248</div><div><span class="" style="white-space:pre"> </span>broadcast 50.7.178.103</div><div><span class="" style="white-space:pre"> </span>network 50.7.178.96</div><div><span class="" style="white-space:pre"> </span>gateway 50.7.178.97</div><div><br></div><div>auto eth0:1</div><div>iface eth0:1 inet static</div><div><span class="" style="white-space:pre"> </span>address 50.7.178.99</div><div><span class="" style="white-space:pre"> </span>netmask 255.255.255.248</div><div><span class="" style="white-space:pre"> </span>broadcast 50.7.178.103</div><div><span class="" style="white-space:pre"> </span>network 50.7.178.96</div><div><span class="" style="white-space:pre"> </span>post-up ip route add <a href="http://50.7.178.96/29">50.7.178.96/29</a> dev eth0:1 src 50.7.178.99 table eth0:1_if</div><div><span class="" style="white-space:pre"> </span>post-up ip route add default via 50.7.178.97 table eth0:1_if</div><div><span class="" style="white-space:pre"> </span>post-up ip rule add from 50.7.178.99 table eth0:1_if</div><div><span class="" style="white-space:pre"> </span>post-down ip rule del from 50.7.178.99 table eth0:1_if</div><div><br></div><div>auto eth0:2</div><div>iface eth0:2 inet static</div><div><span class="" style="white-space:pre"> </span>address 50.7.178.100</div><div><span class="" style="white-space:pre"> </span>netmask 255.255.255.248</div><div><span class="" style="white-space:pre"> </span>broadcast 50.7.178.103</div><div><span class="" style="white-space:pre"> </span>network 50.7.178.96</div><div><span class="" style="white-space:pre"> </span>post-up ip route add <a href="http://50.7.178.96/29">50.7.178.96/29</a> dev eth0:2 src 50.7.178.100 table eth0:2_if</div><div><span class="" style="white-space:pre"> </span>post-up ip route add default via 50.7.178.97 table eth0:2_if</div><div><span class="" style="white-space:pre"> </span>post-up ip rule add from 50.7.178.100 table eth0:2_if</div><div><span class="" style="white-space:pre"> </span>post-down ip rule del from 50.7.178.100 table eth0:2_if</div><div><br></div><div>auto eth0:3</div><div>iface eth0:3 inet static</div><div><span class="" style="white-space:pre"> </span>address 50.7.178.101</div><div><span class="" style="white-space:pre"> </span>netmask 255.255.255.248</div><div><span class="" style="white-space:pre"> </span>broadcast 50.7.178.103</div><div><span class="" style="white-space:pre"> </span>network 50.7.178.96</div><div><span class="" style="white-space:pre"> </span>post-up ip route add <a href="http://50.7.178.96/29">50.7.178.96/29</a> dev eth0:3 src 50.7.178.101 table eth0:3_if</div><div><span class="" style="white-space:pre"> </span>post-up ip route add default via 50.7.178.97 table eth0:3_if</div><div><span class="" style="white-space:pre"> </span>post-up ip rule add from 50.7.178.101 table eth0:3_if</div><div><span class="" style="white-space:pre"> </span>post-down ip rule del from 50.7.178.101 table eth0:3_if</div><div><br></div><div>auto eth0:4</div><div>iface eth0:4 inet static</div><div><span class="" style="white-space:pre"> </span>address 50.7.178.102</div><div><span class="" style="white-space:pre"> </span>netmask 255.255.255.248</div><div><span class="" style="white-space:pre"> </span>broadcast 50.7.178.103</div><div><span class="" style="white-space:pre"> </span>network 50.7.178.96</div><div><span class="" style="white-space:pre"> </span>post-up ip route add <a href="http://50.7.178.96/29">50.7.178.96/29</a> dev eth0:4 src 50.7.178.102 table eth0:4_if</div><div><span class="" style="white-space:pre"> </span>post-up ip route add default via 50.7.178.97 table eth0:4_if</div><div><span class="" style="white-space:pre"> </span>post-up ip rule add from 50.7.178.102 table eth0:4_if</div><div><span class="" style="white-space:pre"> </span>post-down ip rule del from 50.7.178.102 table eth0:4_if</div></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 8 January 2016 at 23:43, Yawning Angel <span dir="ltr"><<a href="mailto:yawning@schwanenlied.me" target="_blank">yawning@schwanenlied.me</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>
> Is there something incredibly simple which I'm simply just not doing<br>
> properly, or is there possibly more going on here than first meets<br>
> the eye?<br>
<br>
</span>Set the `Address` option in each torrc, otherwise tor will guess.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Yawning Angel<br>
</font></span><br>_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
<br></blockquote></div><br></div>