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 <[email protected]> > _______________________________________________ > tinc mailing list > [email protected] > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) _______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
