<div dir="auto">Simple question here...is your backup daemon listening on your tinc interface?<div dir="auto"><br></div><div dir="auto">You can bind services to interfaces and perhaps by default it doesn't listen on 0.0.0.0.</div><div dir="auto"><br></div><div dir="auto">Maybe you already checked and mentioned that in a prior thread not sure.</div><div dir="auto"><br></div><div dir="auto"><br><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Feb 9, 2019, 4:27 AM albi <<a href="mailto:albi@life.de">albi@life.de</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> I'm using something similar to Amazon's VPCs, where a logical group of<br>
> instances has a local subnet from the cloud provider. This local subnet<br>
> is always <a href="http://10.0.0.0/24" rel="noreferrer noreferrer" target="_blank">10.0.0.0/24</a>. As there are multiple VPC's, these private local<br>
> subnets dont collide.<br>
<br>
I do not know what Amazon does, and it looks like I do not want to know<br>
it :-)<br>
<br>
Am I correct? web, gateway and backup have NO direct lan connection and<br>
you want to connect them via tinc.<br>
<br>
If you need the "Amazon way" AND you have no double ips, you can use<br>
tinc in switch mode and use your <a href="http://10.0.0.5/10/101" rel="noreferrer noreferrer" target="_blank">10.0.0.5/10/101</a> ips directly.<br>
But switch means every broadcats will be transportet to every tinc node.<br>
<br>
Normaly you would use 3 different local networks, 10.0.1.x, 10.0.2.x,<br>
10.0.3.x, then you can use tinc in router mode (default).<br>
Again you can just use your local 10.0.x.y ip for tinc and route all<br>
<a href="http://10.0.0.0/16" rel="noreferrer noreferrer" target="_blank">10.0.0.0/16</a> traffic to tinc. Which is done automaticly if you use /16<br>
for tinc network. To be exact, /16 ist far to much, but should work.<br>
<br>
If you want extra ips for tinc, you choose one network, lets say<br>
<a href="http://172.16.0.0/24" rel="noreferrer noreferrer" target="_blank">172.16.0.0/24</a> and just give every node one ip of this network. Then you<br>
can ping each tinc server with this ip but not the 10.0.0.x ips.<br>
<br>
I think gateway will not need 2 ips, you can do alot, but it does not<br>
make things easier :-)<br>
<br>
<br>
ALBI...<br>
_______________________________________________<br>
tinc mailing list<br>
<a href="mailto:tinc@tinc-vpn.org" target="_blank" rel="noreferrer">tinc@tinc-vpn.org</a><br>
<a href="https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc" rel="noreferrer noreferrer" target="_blank">https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a><br>
</blockquote></div>