<div>The "10 megabit" connection that you see is not accurate. The TAP-Win32 adapter will run at hardware and network speed. I believe the reported link speed is just residue from the days when virtual adapters didn't exist. Personally, I've never created a VPN over fast ethernet, but on two endpoints with 20 megabit internet connections, I have seen 17.5 megabits of VPN traffic. Well above the reported 10 megabit link.</div>
<div> </div>
<div>Also, "TCPOnly = yes" is a <a href="http://www.tinc-vpn.org/documentation/tinc_4.html#Host-configuration-variables" target="_blank">Host configuration variable</a>. You have it placed as a <a href="http://www.tinc-vpn.org/documentation/tinc_4.html#Main-configuration-variables" target="_blank">main configuration variable</a> where I don't believe it is doing anything.</div>
<div> </div>
<div>You have "mode = switch" in your main configuration file. I therefore think the "Subnet=" variables in your host configuration files may be irrelevant.<br><br></div>
<div class="gmail_quote">On Thu, Dec 17, 2009 at 8:30 AM, Guus Sliepen <span dir="ltr"><<a href="mailto:guus@tinc-vpn.org">guus@tinc-vpn.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im">On Thu, Dec 17, 2009 at 12:21:25AM +0100, Johann Stieger wrote:<br><br>> response time: how is it possible to increase the response time on Tinc VPNs.<br>> When I use tinc over a fast or giga-bit network connection the ping-response<br>
> time is normally about 1800 to 2000 ms. Sometimes I get ping response times<br>> at about 2.500 to 3.000 ms over a normal Ethernet Connection or a<br>> television-cable connection within the same providers-network in the same<br>
> city. The ping-time on the underlaying network connection is about 10 to 30<br>> ms. So when I use Windows Remote Desktop it is terrible when I have to wait 2<br>> or 3 seconds to wait for a response of the chance of the desktop.<br>
</div>[...]<br>
<div class="im">> I use 3 Windows XP and one Windows Vista Notebooks as client and a Windows Small Business Server 2008 as server. On the client-side the config-file looks like this:<br></div>[...]<br>> Mode=switch<br>
> TCPOnly=yes<br><br>Try running tinc without TCPOnly = yes. If you force TCP, then all traffic will<br>go through a single TCP connection, which can indeed significantly decrease<br>performance. The reason is explained here:<br>
<br><a href="http://sites.inka.de/~W1011/devel/tcp-tcp.html" target="_blank">http://sites.inka.de/~W1011/devel/tcp-tcp.html</a><br><br>If you are not already using tinc 1.0.11, please upgrade. Also, add the<br>following to the host config files:<br>
<br>PMTUDiscovery = yes<br><br>This will let tinc automatically determine the maximum size for UDP packets<br>without fragmentation between nodes, and if UDP traffic is impossible, it will<br>automatically fall back to TCP.<br>
<font color="#888888"><br>--<br>Met vriendelijke groet / with kind regards,<br> Guus Sliepen <<a href="mailto:guus@tinc-vpn.org">guus@tinc-vpn.org</a>><br></font><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.10 (GNU/Linux)<br>
<br>iEYEARECAAYFAksqMoIACgkQAxLow12M2nv1bgCfYWAz+Jb1Boa0bdI1QRu3GZgB<br>sYMAoJxa4qb7Adsr2TDHA157Qs8N6gbx<br>=P+wN<br>-----END PGP SIGNATURE-----<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><br></blockquote></div>
<br>