search for: tenant1

Hi, Guus The use case the shared default gateway for multi-tenant, if that the case the node who own the default gateway will have problem to route with different tenant who has overlapped address scope? Is it true when no any other tools like the namespaces? (tenant1)\ (tenant2)——common node—— shared gw node—— Internet (tenant3)/ But if the each tenant have it’s dedicate default gateway, but the path from the tenant node to the default gateway node will be shared by some common tinc node, then the netname of tinc can handle this, right? I think the common tinc...

...08PM +0800, Bright Zhao wrote: > The use case the shared default gateway for multi-tenant, if that the case the node who own the default gateway will have problem to route with different tenant who has overlapped address scope? Is it true when no any other tools like the namespaces? > > (tenant1)\ > (tenant2)——common node—— shared gw node—— Internet > (tenant3)/ Imagine both tenant1 and tenant2 use IP address 1.2.3.4, and both try to connect to 8.8.8.8. Then return packets from 8.8.8.8 have destination address 1.2.3.4. This is not enough information for the common node to determine...

Hi, Tinc expert For use case of multi-tenancy use case, should I use multiple netnames (/etc/tinc/tenant1, /etc/tinc/tenant2/, etc.) for the network, so that even different tenant have overlapped network address will be possible to work in the same physical host? or can not?

On Tue, May 02, 2017 at 08:46:45PM +0800, Bright Zhao wrote: > For use case of multi-tenancy use case, should I use multiple netnames (/etc/tinc/tenant1, /etc/tinc/tenant2/, etc.) for the network, so that even different tenant have overlapped network address will be possible to work in the same physical host? or can not? If you have multiple netnames, then you can have overlapping network addresses all you like as far as tinc is concerned. However...