<div dir="ltr">As I understood, A and B are on the same network.<br>When the network is cut from the Internet, why wouldn't A and B talk to each other?</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 14, 2018 at 11:45 AM, codl <span dir="ltr"><<a href="mailto:codl@codl.fr" target="_blank">codl@codl.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello list, I have a bug to report<br>
<br>
I have a tinc network of hosts composed of two hosts on a network, let's call them A and B, and a number of remote hosts over the internet, that I'll collectively call C. A and B both ConnectTo each other and to C<br>
<br>
The config files for C refer to them by DNS hostname, while A and B have plain IP addresses. This will be relevant<br>
<br>
When A and B are cut off from the internet, I'd expect A and B to still be able to talk to each other, but in practice it works for a time and then stops working for a few minutes, comes back for a time, etc. Modifying the host config files for C on both A and B to point at IP addresses rather than DNS hosts seems to fix it.<br>
<br>
I suspect that tinc is waiting for DNS requests to time out and not routing any packets in the meantime<br>
______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">https://www.tinc-vpn.org/cgi-<wbr>bin/mailman/listinfo/tinc</a><br>
</blockquote></div><br></div>