Why host-up script triggered even not ConnectTo?
Narcissus Emi
eminarcissus at gmail.com
Mon May 1 09:07:51 CEST 2017
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.
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.
--
Narcissus Emi
日時: 2017年5月1日 14:15:14, Bright Zhao (startryst at gmail.com) が書きました::
> Hi, Tinc Expert
>
> in my tinc.conf, the ConnectTo to host X is commented, like below:
>
> #ConnectTo = X
>
> 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.
>
> Why? What’s the logic behind to trigger host-up? How can I avoid this
> except remove the host-up file?
>
>
> Bright Zhao
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20170501/591b663a/attachment.html>
More information about the tinc
mailing list