Hello: The documentation does not have the following use cases very well defined or described. I have created a PDF file that Tinc-VPN can use to public and I would be happy to make more PDF files for usage with the examples on the web site. There are 2 pages in the PDF file attached, the first page is a production setup and the page is a test setup wholly contained within a single server. IS there someone who is more fluent on configuration files that might share /tinc/serverX/tinc.up abd /tinc/serverX/tinc.conf files that would address both of the included setups. Thanks a bunch, Marco -------------- next part -------------- A non-text attachment was scrubbed... Name: TincVPN-Example.pdf Type: application/pdf Size: 29547 bytes Desc: not available URL: <http://www.tinc-vpn.org/pipermail/tinc-devel/attachments/20141208/e4799785/attachment-0001.pdf>
The use cases that I outlined in the use case examples pdf file are pushing my limits of understanding the documentation as contained in the 1.1pre9 PDF manual. The self contained example is tricky because I created 4 ip-address on the eth0 device (192.168.1.30/31/32/33) so I could test a 4 node VPN that lives entirely within a single server. But the tinc command line utility is written assuming a single host with a single reference instead of 4 hosts stuffed into a single /etc/tinc/netname directory. And this use case is a stepping stone to the multi data center setup that requires route add commands so that local vpn traffic does on the private eth1 interface while the wan vpn traffic exits on the eth0 interface to the outside internet. My goal is to organize both use cases so other users can get started with a ready to go set of files to download and run. The process is a bit confusing since the NETNAME and DEVICE and COMPANY in the examples are a bit confusing. Thank you anybody for your assistance in this matter. Marco On 12/8/2014 6:02 PM, md at rpzdesign.com wrote:> Hello: > > The documentation does not have the following use cases very well > defined or described. > > I have created a PDF file that Tinc-VPN can use to public > and I would be happy to make more PDF files for usage with the examples > on the web site. > > There are 2 pages in the PDF file attached, the first page is a > production setup and the page is a test setup wholly contained within a > single server. > > IS there someone who is more fluent on configuration files that might > share /tinc/serverX/tinc.up abd /tinc/serverX/tinc.conf files that would > address both of the included setups. > > Thanks a bunch, > > Marco > > > > _______________________________________________ > tinc-devel mailing list > tinc-devel at tinc-vpn.org > http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc-devel >
On Mon, Dec 08, 2014 at 11:02:24PM -0500, md at rpzdesign.com wrote:> The self contained example is tricky because I created 4 ip-address on > the eth0 device (192.168.1.30/31/32/33) so I could test a 4 node VPN > that lives entirely within a single server.That's quite hard to do, it's far easier to run four instances of tinc on four different ports on the same machine.> But the tinc command line utility is written assuming a single host with > a single reference instead of 4 hosts stuffed into a single > /etc/tinc/netname directory.The "netname" does not have to be the same on all nodes of a VPN. It is merely a quick way to tell tinc where its configuration data lives and how to name the VPN interface. So in your self-contained example, use four different netnames. If you don't like this, then you should properly simulate four different machines on a single one, either using containers (like LXC) or full virtualisation (like KVM). -- 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: 819 bytes Desc: Digital signature URL: <http://www.tinc-vpn.org/pipermail/tinc-devel/attachments/20141209/bf2cabf3/attachment.sig>