Problem with connecting another subnet
Rafael Wolf
rfwolf at gmail.com
Sat Feb 9 14:52:31 CET 2019
Simple question here...is your backup daemon listening on your tinc
interface?
You can bind services to interfaces and perhaps by default it doesn't
listen on 0.0.0.0.
Maybe you already checked and mentioned that in a prior thread not sure.
On Sat, Feb 9, 2019, 4:27 AM albi <albi at life.de wrote:
> > I'm using something similar to Amazon's VPCs, where a logical group of
> > instances has a local subnet from the cloud provider. This local subnet
> > is always 10.0.0.0/24. As there are multiple VPC's, these private local
> > subnets dont collide.
>
> I do not know what Amazon does, and it looks like I do not want to know
> it :-)
>
> Am I correct? web, gateway and backup have NO direct lan connection and
> you want to connect them via tinc.
>
> If you need the "Amazon way" AND you have no double ips, you can use
> tinc in switch mode and use your 10.0.0.5/10/101 ips directly.
> But switch means every broadcats will be transportet to every tinc node.
>
> Normaly you would use 3 different local networks, 10.0.1.x, 10.0.2.x,
> 10.0.3.x, then you can use tinc in router mode (default).
> Again you can just use your local 10.0.x.y ip for tinc and route all
> 10.0.0.0/16 traffic to tinc. Which is done automaticly if you use /16
> for tinc network. To be exact, /16 ist far to much, but should work.
>
> If you want extra ips for tinc, you choose one network, lets say
> 172.16.0.0/24 and just give every node one ip of this network. Then you
> can ping each tinc server with this ip but not the 10.0.0.x ips.
>
> I think gateway will not need 2 ips, you can do alot, but it does not
> make things easier :-)
>
>
> ALBI...
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20190209/b6e62aa1/attachment.html>
More information about the tinc
mailing list