How to use indirect connections with TunnelServer=yes

Maximilian Stein m at steiny.biz
Tue Dec 7 13:05:37 CET 2021


Hello,

Primarily to mitigate the issue described on Github [1] I am 
experimenting with "TunnelServer=yes".

My topology consists of five central nodes that are connected to each 
other (fully-meshed) while the other nodes ("clients") only connect to 
one or more of the central ones. All nodes have a fully populated 
/etc/tinc/NET/hosts directory, though, so all the public keys and subnet 
declarations are availabe on every host.

When I set "TunnelServer=yes" on the central nodes, however, only 
communication between nodes which are directly connected works. Is this 
the intended effect of TunnelServer?

Since my application relies on communication between the clients, I 
couldn't use the TunnelServer mode is this case.

Best,
Max


[1]: https://github.com/gsliepen/tinc/issues/195

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20211207/72735560/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20211207/72735560/attachment.sig>


More information about the tinc mailing list