"Elton Seng Yan Thung" <(E-Mail Removed)> wrote in message
news:bsrbs2$c4t$(E-Mail Removed)...
> Dear all,
> I have DSL (512kbs) connection and Cable (500+kbs in average)
connection
> at my home. I have connected both of them in my Linux (Redhat 9-2.4.20)
> computer. I heard Linux can bond both connection together to get
> 1) Better bandwidth (500kbs+500kbs=1mb)
> 2) Redundency (in case of one link down)
> I am not expert in Linux but wish to get the experiment done. Wish
> someone to guide me.
> The setting as follow
> Cable from linksys router to eth0 with IP address 192.168.1.6
> DSL connection from DSL router to eth1 with IP address 10.0.0.8
> LAN Connection to eth2 (future NAT to all my clients in my home network to
> enjoy Greater bandwitdh and Non-stop of the Internet)
> The kernel 2.4.20 already with working copy of iproute2 installed.
The
> default path to internet via eth0...
>
> I have tried the following command
> #ip route replace default equalize \
> nexthop dev eth0 \
> nexthop dev eth1
> ip route flush cache.
> Although the default routing table have changed, the internet
connection
> still go via eth0. I really don't know what goes wrong. I wish someone can
> help me.
>
> thanks a lot
>
>
The term for this may be "bandwidth aggregation" or "teaming". I saw some
farily expensive hardware that might do this: Nexland ISB PRO 800 TURBO
http://www.homenethelp.com/web/revie...ro800turbo.asp
ftp://ftp.nexland.com/pub/media/ProAll_Manual.pdf might have useful
information.
Limitations of Connection Teaming
Because of the way Internet protocols work, downloading a single large file
or watching a single streaming video still happens over only one of the WAN
connections leaving the other connection free to service other requests.
Connection teaming is perfect for operations that create many network
connections (like web browsing) but does not do much for operations that
utilize only a single connection - like downloading a file or
video-conferencing. Still, the snappiness of web browsing makes this a great
solution. UPDATE 8/5/2002: Nexland has somewhat overcome this with a
software solution
From Google:
My roomate and I were thinking of doing something similar with Cable and DSL
for (hopefully) more reliable service, not to mention increased bandwidth.
I asked a former coworker about this because i knew he had experience with
bundling dialup connections and here's what he told me.
"I used MPPP with to aggregate multiple dial connections. It groups PPP
frames, and since PPP is a link layer protocol, IP addressing was not a
problem. There isn't a similar protocol for Ethernet/dsl/cable. What can
be done is to have multiple Ethernet/NICs share the same IP address. More
than one IP address can be assigned to an interface, so you can have unique
and shared addresses on one interface. As long as all shared IP addresses
are on the same host - no problems."