Cluster and loadbalanced ADSL

majik

New Member
Joined
Aug 6, 2003
Messages
6
Reaction score
0
Location
.
Have someone perfected this yet....
imagine our internet cost our company R33000 per month over a R1000 per day.
you get 10 ADSL modems that gives you:
30gig limit a month +/-
and gives you a decent 512k.

i am working on it inform or assit me if anyone has been there.

G
 
Most probably you could do even better:

2 ADSL lines, one for International only, and one for all local traffic.

Depends on you peak bandwidth requirments...

The local traffic line will most probably take care of the bulk of your needs leaving very little bandwidth for the international line.

Should not be too difficult to set up with a Linux box.


South Africa needs World Class Broadband at World Competitive Prices.
 
I was thinking of something similar.

How would you handle SSL connections if your IP changes during a session?

How do you round robbin between the lines and avoid those lines that reached their limit?
 
Ai.. everyone always prefers linux... anyhow, it's just as easy to do with a windows box... if not easier. If you already have a Windows 2000 Server computer somewhere, you could do the following (out of a financial perspective, if you don't have Windows, you could opt for the linux solution, but it's a little more tricky, although my advice below will work on both):

This will be on how to configure TWO adsl lines.. one for local, and one for international:

Get a Windows 2000 / NT or linux box you can set up as a router (it can still run other apps as well).

Install two network interfaces, one for your local network, and one for the two ADSL routers (i recommend a d-link or planet type). [I myself use the planet's].

Ip addresses can be configured as follows:
LOCAL: 192.168.0.1
ADSL: 192.168.1.1

Now, set up routing on the box (Quagga in Linux, at network neighborhood in NT 4, and at ROUTING AND REMOTE ACCESS in Win2000).
Configure it to be "a network router".

I'd recommend setting up DHCP on the box as well (just the local LAN card), and configuring the ROUTER and DNS to point to 192.168.0.1.

Now set up DNS on the server, and tell it to forward all the requests to 192.168.1.2 (I'll be coming to this device in just a second).

Configure the local ADSL router to be 192.168.1.2
Configure the international ADSL router to be 192.168.1.3

Connect them all to the 192.168.1.1 adapter, by using a hub/switch (some modems have a 4-port switch built in).

Right... now go into the IP properties of the LAN adapter (the one with the IP: 192.168.1.1) and set the default gateway to: 192.168.1.3.

At this point you should have internet access on all your pc's on the LAN.

Now, the only thing that remains to be done, is to tell the server to pass all local traffic through the 192.168.1.2 adsl router.

So, go into command prompt on the Windows Server, and type the following:
route add 196.0.0.0 MASK 255.0.0.0 192.168.1.2 -p
route add 165.165.0.0 MASK 255.255.0.0 192.168.1.2 -p
route add 146.232.0.0 MASK 255.255.0.0 192.168.1.2 -p

The few routes at the top should already catch the majority of local traffic, but there is still another few IP ranges out there that you can add. I'd recommend adding these, and if you use something a lot and know it's local, add that as well.

I'm running this setup currently, and it's working like a charm. Reply to the post if you need more info.

-Solar
 
oh.. just something else: Remember to set up the two ADSL routers to use 192.168.1.1 as their internal gateway.. or add a route (the planet routers work like this) to: 192.168.0.0 MASK 255.255.0.0 to 192.168.1.1

-Solar
 
[:D]

lol...

Windows is a whole lot more expensive than Linux. A lot less stable and in the end you sacrifice performance for ease of use. Even the excuse that Linux is too complex is not valid anymore seeing as most recent Linux distros have decent GUI's and powerful networking tools.

You will be able to do a whole lot more with Linux (even as a home user) than with Windows. In the end Linux makes you a better computer user where windows makes you stupid. Though the last comment does not aply to you. [8)]

Just a thought...

Cheers
Antowan

<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by Solar</i>
<br />Ai.. everyone always prefers linux... anyhow, it's just as easy to do with a windows box... if not easier. If you already have a Windows 2000 Server computer somewhere, you could do the following (out of a financial perspective, if you don't have Windows, you could opt for the linux solution, but it's a little more tricky, although my advice below will work on both):

This will be on how to configure TWO adsl lines.. one for local, and one for international:

Get a Windows 2000 / NT or linux box you can set up as a router (it can still run other apps as well).

Install two network interfaces, one for your local network, and one for the two ADSL routers (i recommend a d-link or planet type). [I myself use the planet's].

Ip addresses can be configured as follows:
LOCAL: 192.168.0.1
ADSL: 192.168.1.1

Now, set up routing on the box (Quagga in Linux, at network neighborhood in NT 4, and at ROUTING AND REMOTE ACCESS in Win2000).
Configure it to be "a network router".

I'd recommend setting up DHCP on the box as well (just the local LAN card), and configuring the ROUTER and DNS to point to 192.168.0.1.

Now set up DNS on the server, and tell it to forward all the requests to 192.168.1.2 (I'll be coming to this device in just a second).

Configure the local ADSL router to be 192.168.1.2
Configure the international ADSL router to be 192.168.1.3

Connect them all to the 192.168.1.1 adapter, by using a hub/switch (some modems have a 4-port switch built in).

Right... now go into the IP properties of the LAN adapter (the one with the IP: 192.168.1.1) and set the default gateway to: 192.168.1.3.

At this point you should have internet access on all your pc's on the LAN.

Now, the only thing that remains to be done, is to tell the server to pass all local traffic through the 192.168.1.2 adsl router.

So, go into command prompt on the Windows Server, and type the following:
route add 196.0.0.0 MASK 255.0.0.0 192.168.1.2 -p
route add 165.165.0.0 MASK 255.255.0.0 192.168.1.2 -p
route add 146.232.0.0 MASK 255.255.0.0 192.168.1.2 -p

The few routes at the top should already catch the majority of local traffic, but there is still another few IP ranges out there that you can add. I'd recommend adding these, and if you use something a lot and know it's local, add that as well.

I'm running this setup currently, and it's working like a charm. Reply to the post if you need more info.

-Solar





<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

He who does not understand the value of war at the right time, cannot comprehend the value of life at any time - Anonymous
 
Top
Sign up to the MyBroadband newsletter
X