From the tinc page: "*Automatic full mesh routing-* 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." That's exactly what's not working for me. Let me illustrate: Both nodes B and C have ConnectTo statements to connect to node A. Node A only listens. A-C and A-B traffic are normal. But, I see activity on Node A's outside interface (eth0) on port 655 during B-C traffic. The ping times reflect an intermediate hop as well. I've played with the IndirectData option, but it doesn't seem to have any affect. Perhaps I haven't played enough. I've solved the issue by configuring all 6 nodes in the real network to have ConnectTo statements to the other 5. If I read the automesh statement correctly, it shouldn't have to be that way, no? Thanks in advance, Jeff Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site: http://tinc.nl.linux.org/
On Thu, Nov 27, 2003 at 12:12:30PM -0500, Jeff Pyle wrote:> I've played with the IndirectData option, but it doesn't seem to have > any affect. Perhaps I haven't played enough. I've solved the issue by > configuring all 6 nodes in the real network to have ConnectTo statements > to the other 5. If I read the automesh statement correctly, it > shouldn't have to be that way, no?No, you shouldn't have to do that. Do you have TCPOnly = yes in your config files or are some hosts connected via IPv4 and others via IPv6? -- 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/20031127/4b7c5932/attachment.pgp