Hello list, I have a bug to report 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 The config files for C refer to them by DNS hostname, while A and B have plain IP addresses. This will be relevant 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. I suspect that tinc is waiting for DNS requests to time out and not routing any packets in the meantime
As I understood, A and B are on the same network. When the network is cut from the Internet, why wouldn't A and B talk to each other? On Wed, Mar 14, 2018 at 11:45 AM, codl <codl at codl.fr> wrote:> Hello list, I have a bug to report > > 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 > > The config files for C refer to them by DNS hostname, while A and B have > plain IP addresses. This will be relevant > > 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. > > I suspect that tinc is waiting for DNS requests to time out and not > routing any packets in the meantime > _______________________________________________ > 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/20180315/95b95279/attachment-0001.html>
On Wed, Mar 14, 2018 at 03:45:50PM +0100, codl wrote:> 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 > > The config files for C refer to them by DNS hostname, while A and B have plain IP addresses. This will be relevant > > 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. > > I suspect that tinc is waiting for DNS requests to time out and not routing any packets in the meantimeThat's indeed the problem. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20180315/b374f910/attachment.sig>
Right. Would it be possible to move DNS resolution to a different thread or something so it doesn't block everything else? On Thu, 15 Mar 2018, at 22:47, Guus Sliepen wrote:> On Wed, Mar 14, 2018 at 03:45:50PM +0100, codl wrote: > > > 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 > > > > The config files for C refer to them by DNS hostname, while A and B have plain IP addresses. This will be relevant > > > > 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. > > > > I suspect that tinc is waiting for DNS requests to time out and not routing any packets in the meantime > > That's indeed the problem. > > -- > Met vriendelijke groet / with kind regards, > Guus Sliepen <guus at tinc-vpn.org> > _______________________________________________ > tinc mailing list > tinc at tinc-vpn.org > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature)