From: Brady, Padraig (Padraig.Brady at domain compaq.com)
Date: Mon 04 Oct 1999 - 14:23:22 IST
Just to clarify that the virtual connection suggestion
actually creates 2 seperate dialup connections (2 ip addresses)
as opposed to transparently merging the 2 Bchannels using a lower
layer (2) protocol.
Therefore this will be useful if you have many HTTP clients
sharing the virtual connection (as all the requests for pages
and graphics etc can be shared across the 2 connections).
However it's completely useless for a large FTP download
as this is a persistent connection for the whole data transfer
which will only go over 1 of the Bchannels.
Note also that true multilink is usually cheaper than making
> -----Original Message-----
> From: Vincent Cunniffe [mailto:vcunniff at domain arbgroup.com]
> Sent: 04 October 1999 14:09
> Niall O Broin wrote:
> > Channel bonding requires support on both ends of the link.
> I've a suspicion
> > that you should be able to do it by making two single
> connections and doing
> > the bonding at a low level on the Linux box but this
> probably requires advanced
> > kernel wizardry and lots of time.
> You can do it unilaterally to some extent :
> 1) Create two dialup 64kb ISDN connections
> 2) Create a virtual connection (EQL module), and add the two
> real ISDN 64k channels.
> 3) Run all comms through the virtual channel.
> This will give you a single 128kb channel, which will be
> transparent to
> users with the caveat that no *single* thread will be able to
> carry more
> than 64k. If you want a truly transparent link, you'll need
> on the part of the ISP.
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:04:39 GMT