Well, you can get pretty close to this.  Check out the Nexland routers:

http://www.nexland.com/turbo.cfm

They can load balance two separate connections.  I don't believe this works
for a "single" FTP transfer, for example... it works by loadbalancing
separate transfers.  Things like surfing, multi-part transfers, etc. all
happen at 2x the speed.

I've never used one of these before, but I know that you can do
load-balancing-like activities without any coordinateion on the ISP side.

Fatpipe Networks also makes similar boxes, although it seems they are more
targeted towards businesses:

http://www.fatpipeinc.com/

Jared Valentine
[EMAIL PROTECTED]

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of S Woodside
Sent: Tuesday, April 01, 2003 10:43 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [BAWUG] I have a dream


Well, it's a fairly minor dream. What I imagine is this: I have DSL. My
neighbour has DSL. We also both have WiFi APs that can reach each
other, and connect at order-of-magnitude faster than the DSL links.
What I dream is this: That we start routing internet across the link.
When I start pulling packets off the internet, they can come to me not
only through my own DSL but from hers as well. I think this boils down
to an ultimate simplicity what all FN / CWNers want to achieve.

What needs to happen before I can realize my dream. I need to get an
IPv6 address ... at least one ... for free. I need to be able to set up
multi-homing in my home router. I need to be able to advertise my
routing path to the internet. The internet needs to be able to handle
at a massive scale (since every neighbour connects...). We need a /lot/
more IP addresses than we have now. I need to use a /real/ IP address
because I can't route internet traffic through a NAT/site-local
address. I need to have an ad-hoc routing algorithm that can set up
this bridge and route across it really easily (because I'm not a
trained network admin). Forget about BGP, AS, etc., we need a way to
handle the massive overload of routes at local scale, at a regional
scale, at a global scale -- something that will scale gracefully as the
internet topology shifts from a tree to a massively connected mesh.

Please comment ... tell me what you think.

Simon

PS I'm cross-posting this to a bunch of lists because I don't know one
it belongs on. If you think you know which is best, please tell me!

--
general wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless

--
general wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless

Reply via email to