<html><head></head><body>X-up is being called when any connection is being built between node A and node X, it doesn't have anything to do whether you have connectTo in the config file or not.<div>Because tinc is a mesh network, if node A have a direct connection to node B, and node B have a connection to node X, you can have a connection between A and X, and X-up is being called at the moment when it built a connection on demand.<br> <br><div class="bloop_sign"><div>-- <br>Narcissus Emi</div></div> <p class="gmail_quote" style="color:#000">日時: 2017年5月1日 14:15:14, Bright Zhao (<a href="mailto:startryst@gmail.com">startryst@gmail.com</a>) が書きました::</p> <blockquote type="cite" class="gmail_quote"><span><div><div></div><div>Hi, Tinc Expert<br><br>in my tinc.conf, the ConnectTo to host X is commented, like below:<br><br>#ConnectTo = X<br><br>and there is a script: /etc/tinc/netname/hosts/X-up, I thought commented the ConnectTo X wouldn’t trigger the X-up, but it did.<br><br>Why? What’s the logic behind to trigger host-up? How can I avoid this except remove the host-up file?<br><br><br>Bright Zhao<br>_______________________________________________<br>tinc mailing list<br><a href="mailto:tinc@tinc-vpn.org">tinc@tinc-vpn.org</a><br><a href="https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc">https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a><br></div></div></span></blockquote>
</div></body></html>