On Thu, Jun 21, 2012 at 10:02:02AM +0800, Xuefer wrote:
> the situation has gone worst then ever since a long time ago. some ISP
> normally don't block udp, but when traffic is high, udp get lower
priority
> and packet loss happens. some ISP slowdown tcp connection if it is
> used aggressively. when this happens, i have to block udp using iptables
> and use tcp only for tinc, or re-dial pppoe
> also, multiple thread (tcp) downloading "tech" is used years ago
to speed
> up downloading
>
> i would like to see multiple udp/tcp connection be used in tinc. by
> using configuration like "Address = UDP:1.2.3.4:2000~2010,
> TCP:1.2.3.4:2000~2010".
> i cannot go into the detail how it could be implemented to get most
> advantage out of
It seems the Internet is getting crazier every day. Tinc was originally written
with the assumption that the real network just worked as it should, and only
provided encrypted tunneling for your private network. It was not designed to
fix your network. It seems that the way forward these days is to just
spread-spectrum spam the network with IP packets of every type and all port
numbers, and see what sticks...
I might add such a feature to tinc in the future. Meanwhile, I suggest you
complain to your ISP, and if that is possible for you, switch or threaten to
switch to another ISP.
You can also try to set up multiple instances of tinc on each node of your VPN,
with almost identical configurations except for the Port they are listening on,
and use the bonding driver to spread packets out over all of them. If that
prevents the ISP from dropping packets, it might improve your VPN's
performace.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20120621/d96d434d/attachment.pgp>