I have a simple 3 hosts virtual network setup with tinc vpn. Three hosts are using ips as A-10.0.0.1, B-10.0.0.2, and C-10.0.0.3. All 3 hosts(A,B,C) are in three different networks. B and C uses "ConnectTo" in their tinc.conf to connect to A's external IP. After all the setups are done, such as key exchanges etc, and start the tinc daemon on all hosts, the connections among the 3 hosts are working with their ips defined above. My question is that, once the initial connections are established, can B and C talk to each other directly without going through A? What if A is down, can B and C continue talking to each other? With the simple setup I have now, it does not work if I shut down A. Is it possible with some configure changes, I can have A to instruct B and C to communicate directly with each other? I am trying to get B and C to work as a pair of P2P hosts. Thanks, Philip -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20191015/a345efd0/attachment.html>
On Tue, Oct 15, 2019 at 11:18 AM philip shangguan <pshangguan at gmail.com> wrote:> My question is that, once the initial connections are established, can B and C talk to each other directly without going through A?Are B and/or C behind a firewall? You should be able to see which tinc nodes are connected to which other nodes by running tinc in debug mode: tincd -n [network-name] -D -d> What if A is down, can B and C continue talking to each other?If B can directly connect to C (or vice versa), then B and C should still be able to communicate directly with each other.>With the simple setup I have now, it does not work if I shut down A. Is it possible with some configure changes, I can have A to instruct B and C to communicate directly with each other?> I am trying to get B and C to work as a pair of P2P hosts.I believe tinc always tries to route packets directly. So your goal should be possible. -Parke
Reasonably Related Threads
- 4 questions about tinc's VPN
- Tinc on PFSENSE box can join mesh, share keys, connect out, but doesn't reply to pings or connections
- Multiple default gateway from tinc node
- Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1
- Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1