Is it possible to get two ADSL lines to work together to increase up-stream bandwidth w/o the help of your ISP(s)? Yes. Is it easy? No. Will it actually double your bandwidth? No. Are you better off finding another solution? Yes.
There are a variety of ways you could make this work, but none of them are going to do quite what you want. You could wrap your regular connections in a virtual interface that load balances packets over two different interfaces, and then have a similar setup on the server that is receiving the packets. This solution will end up only getting you a slight improvement in bandwidth because of the overhead you are going to have in wrapping the other connections. In addition, you will lose latency.
If you aren't tied to FTP in particular, you could hack together a BitTorrent setup where your home machine seeds your files on both public IPs, and your server can then download different fragments of the file from both connections simultaneously. If this is an option, you could set up a private BitTorrent tracker on your server and bond together dozens of ADSL circuits if you wanted to. You'll piss your ISP off if they figure out what your're up to though. You would probably want to write a shell script or something to set up the .torrent, push it to the server (via rsync or some such), and then cause the server to initiate a bt download.
Greg Brooks wrote:
Anyone successfully used link aggregation to combine two ADSL lines for greater outbound bandwidth?
Because it's asymmetrical bandwidth, I'm fine for inbound speed. but I need to regularly move large files to FTP, and it's becoming an issue.
So, if I'm moving data from a single user (me) to a single point (an FTP site), does link aggregation double my bandwidth? I understand how it would work in multi-users-to-the-net environments, but can't quite get how (or if) it would work in this scenario.
I really don't want to pay the $1025/mo for a T1 line to the house, but it's my only other option.
Any help much appreciated.
Thanks, Greg
Kclug mailing list [email protected] http://kclug.org/mailman/listinfo/kclug