A FAQ: is it mandatory to include the local IP address classes in the global VPN address class?

[Guus Sliepen]

On Thu, Sep 07, 2017 at 10:35:36AM +0300, Răzvan Sandu wrote:

> Since the present tinc documentation is not very clear about this, please
> explain the following: is it mandatory to include the local IP address
> classes in the global VPN address class?

Nothing is mandatory with tinc.

> Is it *mandatory* to use a VPN global addreess class (192.168.0.0/16 on the
> myvpn virtual interface) that *includes* the local LANs (each
> 192.168.x.0/24s on the eth1 interface) - as explained into various pieces
> of tinc documentation and examples?
> 
> Or can we have 192.168.x.0/24s on the local LANs and another, *different*
> private class (say 10.0.0.0/8) common all the myvpn interfaces over the VPN?

Yes, you can do that as well. Note that in router mode, you have to then
provide two Subnets in each host config file; one for that node's
192.168.x.* address, and another for its 10.* address range.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20170907/8623a3a4/attachment.sig>