From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Taylor Date: Thu, 26 Jul 2007 14:30:51 +0000 Subject: Re: [LARTC] Definitive way to aggregate bandwidth using multiple links Message-Id: <46A8B01B.8030000@riverviewtech.net> List-Id: References: <4qdln4-tl7.ln1@tux.abusar.org> In-Reply-To: <4qdln4-tl7.ln1@tux.abusar.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: lartc@vger.kernel.org On 07/26/07 00:55, D=E2niel Fraga wrote: > Mayeb some kind of bonding, but the problem is that the 2 points of=20 > your VPN aren't directly connected, otherwise you could use Bonding=20 > or TEQL. There's EQL for serial links, but you'd have to install it=20 > on both ends... *nod* The only thing that comes to mind that would facilitate true aggregation=20 of multiple links would be to have a server on very high bandwidth that=20 you could create multiple tunnels (IPIP / IPSec / GRE) to and have it=20 aggregate the multiple tunnels together and then use the aggregated=20 tunnel as your larger pipe to the world and do all your NATing at that=20 end so the world would see you from one largish connection. At least in theory this is sound with Multi-Link PPP. However I do not=20 know of any one that has done this. I suppose this would be a decent=20 service if someone could make it turn key. Would any one care to=20 jointly work on something like this? I could locate a box on an OC-3=20 for testing purpose, but not long term production, at least not with out=20 paying hundreds per month. I suppose such a service should support IPSec, IP in IP, GRE, L2TP, PPTP=20 tunnels. What else? Would it be better to aggregate the tunnels in to=20 one large logical router or rather multiple smaller UML / VMWare routers=20 per client so the client could have control over the remote end? What=20 about IP address space? Thoughts / Opinions? Grant. . . . _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc