Internet with two ISP in Suse Linux 10.3

10 pts.
Tags:
ISP
LAN
Network Card
Routers
SUSE Linux
Hi, I have two ISP for internet in SUSE Linux 10.3, the target is to provide redundancy and improve the bandwith 512 KB x 2. I have three network Card, two for the ISP and one for the LAN, my question is the follow: 1.What is the procedure to configure the two target from the ISPs to get the redundancy in SuSe Linux? 2. do I need to configure a bonding? and How I do it? 3. How configure the route for the two ISP? regards Yreal
ASKED: May 23, 2008  2:35 PM
UPDATED: May 23, 2008  2:57 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Take a look at this advanced routing <a href=”http://tldp.org/HOWTO/Adv-Routing-HOWTO/”>How-To</a>. Consider chapters 3 & 4.

Basically, you need to add rules to state that what comes in an interface also goes back out the same one…
And if you are NATting ok, the reverse is always true…

The HOWTO also explains how to do a basic load balance using the ‘weight’ keyword, but there doesn’t appear to be another ‘ip route’ option. Of course you can use the iptables mangle table to mark the outgoing packets and ‘ip rule’ against that mark.

So one basic config is as it’s written in the HOWTO, but I have 5 possible outgoing interfaces, 2 under ‘weight’ control and the others under MARK control.

A 3 interface example:

Name the ‘tables’, one for each interface, ds1, dsl2, dsl3 (chapter 4.1 3rd example)
echo 200 dsl1 >> /etc/iproute2/rt_tables
echo 201 dsl2 >> /etc/iproute2/rt_tables
echo 202 dsl3 >> /etc/iproute2/rt_tables

Jump down to chapter 4.2.1 Split access, and make routes in the tables
based on the interfaces & ip numbers & gateways

ip route add dsl1_network dev eth1 src eth1_ip_number table dsl1
ip route add dsl2_network dev eth2 src eth2_ip_number table dsl2
ip route add dsl3_network dev eth3 src eth3_ip_number table dsl3

and gateway routes…
ip route add default via dsl1_ip_number table dsl1
ip route add default via dsl2_ip_number table dsl2
ip route add default via dsl3_ip_number table dsl3

Now the regular routes.. (= table routes minus the tables)
ip route add dsl1_network dev eth1 src eth1_ip_number
ip route add dsl2_network dev eth2 src eth2_ip_number
ip route add dsl3_network dev eth3 src eth3_ip_number

The default routes load balanced (kind of) for outgoing..
ip route add default scope global nexthop via dsl1_ip_number dev eth1 weight 5 nexthop via dsl2_ip_number dev eth2 weight 5 nexthop via dsl3_ip_number dev eth3 weight 5

And finally the rules of who comes from where..
ip rule add from eth1_ip_number table dsl1
ip rule add from eth2_ip_number table dsl2
ip rule add from eth3_ip_number table dsl3

There are usually places in the ifup/down scripts to place config file statements to do all this at boot or net restart. You may have to use replace instead of add to remove old route statements…

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following