<div>Hi AlBI,</div>
<div> </div>
<div>Well TCPOnly = yes assumes IndirectData = yes so you actually only need to set the TCPData flag.</div>
<div> </div>
<div>TCP does work, but the throughput is cut significantly. I don't have packet loss so TCP is extra traffic and overhead that I don't need.</div>
<div> </div>
<div>The problem I'm receiving now is not a NAT problem.</div>
<div> </div>
<div>Regards,</div>
<div>Donald<br></div>
<div class="gmail_quote">On Fri, Mar 6, 2009 at 2:17 AM, Albi Rebmann <span dir="ltr"><<a href="mailto:albi@life.de">albi@life.de</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">> For months I've been using tinc in TCPOnly because I always received the<br>> unknown host error when using UDP.<br>> On Monday, i set the flag IndirectData = yes in my host files, and removed<br>
> the TCPOnly line.<br><br></div>I have simple rule for using tcponly and indirectaata.<br>If the computer has externl ip, no NAT router between, remove them and use<br>udp.<br>If you have NAT router between tinc server/computer and internet, use both<br>
flags (set yes).<br><br>This works for 5 years now :-)<br><br><br>ALBI...<br><br><br>_______________________________________________<br>tinc mailing list<br><a href="mailto:tinc@tinc-vpn.org">tinc@tinc-vpn.org</a><br><a href="http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc" target="_blank">http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a><br>
</blockquote></div><br>