Combining bandwidth is fairly easy to do. The trick is to get a good guess at the transit time of your packets. The simple way to do this is by stream - for example each http session goes down a separate stream. Also running masquerading on each interface helps.
On Mon, 2007-07-02 at 12:00 -0700, [EMAIL PROTECTED] wrote: ... > Today's Topics: > > 1. Re: Slurpr - the future of the wireless bandwidth pig (A. Khattri) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 2 Jul 2007 00:11:01 -0400 (EDT) > From: "A. Khattri" <[EMAIL PROTECTED]> > Subject: Re: [nycwireless] Slurpr - the future of the wireless > bandwidth pig > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > On Tue, 29 May 2007, Jon Baer wrote: > > > -snip- > > At this moment I can see 8 different signals. Some are closed > > networks but most are open and available. I can only connect to one > > at a time so I tend to just pick the one with the best signal. But > > what if I could connect to all the networks at the same time and > > combine their bandwidth? > > -snip- > > Only problem being that some protocols just won't work over multiple links > because that means you could have packets from one flow coming from > potentially different IPs. Ssh probably won't like that very much :-) > > If you could aggregate all those links and have traffic go through a > single proxy (so its all from one IP) that's a potential avenue to > explore... > > > -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
