DSL link aggregation?

[Bradley Hook]

Greg Brooks wrote:
> * Unsophisticated users who are comfy with FTP and don't want to learn new
> tools.

If the "unsophisticated users" are the ones doing the downloading, then
they can still use FTP to download. Your problem was with uploading.
Once the file is on the server, it can be downloaded by any mechanism
you set up. If your "unsophisticated users" are in your local shop, then
you could set up a local FTP server that will automatically push files
up to your off-site server when they are dropped in a specific location.
If your clients are uploading the files to you, then I don't get why
it's your concern how their connection is set up.

> * Many different clients who need the bandwidth boost, so a point-to-point
> solution isn't a good fit.

Do you have many clients uploading? Or just many clients downloading,
and you doing all of the uploading? If you are the only one uploading,
then it isn't much of a problem.

There are many creative solutions you could set up. The question is if
the time and effort to set it up and make it transparent to your users
is worth saving a few hundred bucks a month.

> -----Original Message-----
> From: Bradley Hook [mailto:bhook at kssb.net] 
> Sent: Wednesday, May 07, 2008 5:21 PM
> To: gregb at west-third.com
> Cc: kclug at kclug.org
> Subject: Re: DSL link aggregation?
> 
> 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
>> Kclug at kclug.org
>> http://kclug.org/mailman/listinfo/kclug
>>
>>
> 

-- 
~Bradley Hook
Education Systems Administrator
Kansas State School for the Blind
1100 State Avenue
Kansas City, KS 66102
Voice: (913) 281-3308 ext. 363
Mobile: (913) 645-9958
Facsimile: (913) 281-3104
http://www.kssb.net

******************************************************************************************
Confidentiality Statement:
This message and accompanying documents are covered by the Electronic
Communications Privacy Act, 18 U.S.C. 2510-2521, and contain information
intended for the specified individual(s) only.  This information is
confidential unless explicitly indicated otherwise.  If you are not the
intended recipient or an authorized agent responsible for delivering it
to the intended recipient, you are hereby notified that you have
received this document in error and that any review, dissemination,
copying, or the taking of any action based on the contents of this
information is strictly prohibited.  If you have received this
communication in error, please notify the sender immediately by E-mail,
and delete the original message.
******************************************************************************************