I currently have 3 ADSL lines which I have a linux box with 4 nics which does load balancing over the 3 connections. Now I can utilize all of the bandwidth when doing multi-threaded downloading but I was hoping to find a way I could get the complete bandwidth of all 3 connections when communicating to a collocated server I have over 1 thread. I don't need this for every site/server I access but I guess if I get this working then I could do that if I just have all my traffic routed via proxy to the colocated server. I am basically trying to find out a way if I can setup some sort of tunnel, or PPP/VPN link between my home computer (with the 3 connections) to the colocated server where traffic over that VPN/tunnel/PPP link (whatever it may be) utilizes all 3 connections. Anyway to do this or anyone have any ideas?

It is called bonding. You need routers and switches that support it on both ends. I don't think it would work over dsl lines however. You don't need the extra bandwith between the host and the modem. To increase the bandwith, your best bet may be to upgrade your service.

Here is a bonding howto:
http://www.cyberciti.biz/howto/quest...iver-howto.php

It is used mainly for high availability and load balancing.

There is no way to 'upgrade my service' All of my lines are 6016/768 kilobits which you can't get DSL at a higher speed here in the U.S. I know it would be possible (just not sure if anyone has tried before) to setup a VPN or tunnel which uses multiple connections/threads. I am simply searching for a way to get a multi-threaded tunnel/vpn/ppptp connection whatever it might be to the colocated server I have. I don't really need the lines to be bonded but the end result would be speeds similar to what my line would be at if they were bonded. For example, I can get my maximum speed (just over 16 megabits) when using a download accelerator that opens multiple connections via FTP. What I would like to do is setup something where I can do the same via sftp/scp and possibly other protocols as well (not just FTP).

i guess what options you have depend a lot on what kind of hosting you are using etc... the first port of call would be lartc http://www.lartc.org/howto/lartc.rpd...ple-links.html or course, but you're clearly aware of things like that already. in which way to you want to use this bandwidth? i can imagine that you'd just like to have both up and down from one site using all links... to that end i would imagine that you should be able to establish x seperate VPN's and then resort to lartc again but routing on those VPN interfaces, not the physical interfaces. this would be assuming you have box to box vpn's but with each vpn using different public peer addresses. i'll admit that i've not really got to grips with vpn's yet, but i'd like to think you should be almost able to just put a bond0 across all the vpn links and just directly bond those connections at both ends, which when you do have such control over both endpoints should be manageable, as i don't expect that each vpn link would require a stateful connection.

if you only want things in one direction i.e. out over the dsl links then a simple routing logic straight out of lartc should suffice, as nothing upstream should be stateful, so won't care if it's just seeing unmatched packets leaving each dsl link to the net.