Hi Everyone, Could someone tell me whether Tinc builds its own routing table to 'hop' between LANs? e.g. LAN A <--> LAN B <--> LAN C Would Tinc resolve a path between LAN A and LAN C automatically (i.e. to hop over LAN B)? Or would I need to setup routing tables for this myself? Thanks very much for any help :-) John _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web!
On Sat, Dec 03, 2005 at 09:02:58AM -0500, John Halfpenny wrote:> Could someone tell me whether Tinc builds its own routing table to 'hop' between LANs? > > e.g. > > LAN A <--> LAN B <--> LAN C > > Would Tinc resolve a path between LAN A and LAN C automatically (i.e. to hop over LAN B)? > > Or would I need to setup routing tables for this myself?Tinc will automatically resolve the path between LAN A and C, but instead of hopping over B, A will communicate directly with C. -- 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/20051205/a3d6105b/attachment.pgp
>> Could someone tell me whether Tinc builds its own routing table to 'hop' between LANs? >> >> e.g. >> >> LAN A <--> LAN B <--> LAN C >> >> Would Tinc resolve a path between LAN A and LAN C automatically (i.e. to hop over LAN B)? >> >> Or would I need to setup routing tables for this myself?> Tinc will automatically resolve the path between LAN A and C, but instead > of hopping over B, A will communicate directly with C.Great! Thanks Guus! John _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web!