<div><div dir="auto">I don't know why, but for my case, I reduced the tinc topology from a complex one(which provide layered redundancy) to a very simpled one(one connection), and that connection drop disappeared.</div><div dir="auto"><br></div><div dir="auto">Later, let me draw the topology and share the config to you to see if there's any findings of the cause.</div><br><div class="gmail_quote"><div>Guus Sliepen <<a href="mailto:guus@tinc-vpn.org">guus@tinc-vpn.org</a>>于2017年9月14日 周四上午3:20写道:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Sep 13, 2017 at 08:02:11PM +0100, Etienne Dechamps wrote:<br>
<br>
> It seems like that kind of problem could be solved by making sure that tinc<br>
> continues PINGing over TCP metaconnections even when an UDP tunnel is<br>
> established, to keep the metaconnection alive. In fact I was under the<br>
> impression that the 1.1 branch already did that or that I had submitted<br>
> some code to do that at some point in the past, but it looks like I maybe<br>
> be misremembering things.<br>
<br>
Tinc always sends regular PINGs over its metaconnections, regardless of<br>
what happens with UDP. This has been the case at least since 1.0 was<br>
released.<br>
<br>
--<br>
Met vriendelijke groet / with kind regards,<br>
Guus Sliepen <<a href="mailto:guus@tinc-vpn.org" target="_blank">guus@tinc-vpn.org</a>><br>
_______________________________________________<br>
tinc mailing list<br>
<a href="mailto:tinc@tinc-vpn.org" target="_blank">tinc@tinc-vpn.org</a><br>
<a href="https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc" rel="noreferrer" target="_blank">https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a><br>
</blockquote></div></div><div dir="ltr">-- <br></div><div class="gmail_signature" data-smartmail="gmail_signature">Sent from iPhone</div>