<div dir="ltr"><div>Hi Andrê,</div><div><br></div><div>So by nodes I assume you mean the "boxes".</div><div>I would suggest each "box" gets it's own tinc node(with a static ip) and then on the server it should be a matter of pointing at the ip address of the appropriate box tinc ip address.</div><div><br></div><div>I've done this myself with WireGuard and it works great.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 25, 2019 at 7:14 AM André Rodier <<a href="mailto:andre@rodier.me">andre@rodier.me</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
I need to build a VPN, and I am not sure if tinc is the right tool to<br>
use. I am more familiar with OpenVPN.<br>
<br>
I have a few boxes at home, behind a router with a dynamic IP<br>
address. Those boxes host some services, like web sites, for instance.<br>
<br>
I have a server hosted online, with a few IPv4 and IPv6 addresses. All<br>
addresses being static, of course.<br>
<br>
I am planning to use tinc on Debian, to "expose" the services hosted on<br>
these "home" boxes on IPv4/IPv6 addresses, using tinc VPN. The NAT<br>
would occur in the tunnel. I can write the nat/masquerade rules.<br>
<br>
The big question is, does tinc need the two nodes have a static IP<br>
address ?<br>
<br>
I don't want to modify the router configuration or to create nat rules<br>
in the home router.<br>
<br>
Thanks,<br>
André<br>
<br>
_______________________________________________<br>
tinc mailing list<br>
<a href="mailto:tinc@tinc-vpn.org" target="_blank">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-bin/mailman/listinfo/tinc</a><br>
</blockquote></div>