Hi.
I read that one feature of tink vpn solution is the Automatic Full Mesh
Routing support that is defined as: "regardless of how you set up the
tinc daemons to connect to each other, VPN traffic is always (if
possible) sent directly to the destination, without going through
intermediate" hops.
What this means?
I don't understand how this work. Can you please give me some
information about it?
I have the following problem. I have an ad-hoc network, for example five
laptop A, B, C, D, E. They are connected in the following manner:
A -------- B-----------C
|
|
|
D
|
|
|
E
This mean that, for example, that node A can reach node D through B,
that is B is the gateway for node A to reach node D.
Now I want that the traffic from node A to node D is encrypted. So I
think to set up a multipoint VPN. That means, that each node sets up a
VPN with its gateway to reach the other nodes.
In the example above node A configures a VPN with node B (the gateway to
reach the other nodes), node B sets up a VPN with node C (its gateway to
reach the other nodes) and so on.
In order to allow the traffic from node A to node D (distant more than
two hops) to pass encrypted, I need to configure VPN in tunnel mode.
My question is: is this configuration possible using tink solution?
The mesh feature is needed?
Very thanks in advanced.
Luciana
Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
===================================================================CONFIDENTIALITY
NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
===================================================================--------------
next part --------------
An HTML attachment was scrubbed...
URL:
http://brouwer.uvt.nl/pipermail/tinc/attachments/20051031/505bec31/attachment.html
On Wed, Nov 02, 2005 at 10:12:44AM +0100, Costa Luciana wrote:> I read that one feature of tink vpn solution is the Automatic Full Mesh > Routing support that is defined as: "regardless of how you set up the > tinc daemons to connect to each other, VPN traffic is always (if > possible) sent directly to the destination, without going through > intermediate" hops. > > What this means? > > I don't understand how this work. Can you please give me some > information about it?It is simple: if you have three nodes, A B and C, and A is connected to B, and B to C, then if A wants to send something to C, it will automatically set up a direct connection between A and C, bypassing node B.> I have the following problem. I have an ad-hoc network, for example five > laptop A, B, C, D, E. They are connected in the following manner:[...]> My question is: is this configuration possible using tink solution?Yes.> The mesh feature is needed?The mesh feature is always on in tinc. It is not necessary for your setup, but it improves performance. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus@sliepen.eu.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20051102/73b2acfb/attachment.pgp