Hello Everyone, Hope everyone is doing well. First off I would like to say that Lartc has been an invaluable source of information for me, I was looking for a solution and a bit of google''ing found this wonderful HOW-TO. So now down to the Question: I have three Internet connections, (Soon to be four if I can get this working) ETH0 - 2mb/2mb ETH1 - 7mb/1mb ETH2 - 7mb/1mb I wish to get these connections load balanced for outgoing traffic, and I''ve hit a small problem. eth0 and eth2 are balancing just fine, doing what they are suppose to. eth0 takes most of the connections and eth2 picks up the slack (Perfect). However eth1 is not sending out "ANY" outgoing information unless its connected directly to. I followed the How-To, however its only based on Two Internet connections. I''m guessing I''ve just made an error when trying to setup three connections. Any help would be great. System information: Fedora Core release 2 (Tettnang) Kernel 2.6.5-1.358 Config File (IPs have been changed slightly to protect their anonymity) ip route add 23.215.3.16/28 dev eth0 src 23.215.3.20 table T1 ip route add default via 23.215.3.17 table T1 ip route add 23.215.4.0/26 dev eth2 src 23.215.4.61 table T2 ip route add default via 23.215.4.1 table T2 ip route add 23.215.16.0/21 dev eth1 src 23.215.17.54 table T3 ip route add default via 23.215.16.1 table T3 ip route add 23.215.3.17 dev eth0 src 23.215.3.20 ip route add 23.215.4.1 dev eth2 src 23.215.4.61 ip route add 23.215.16.1 dev eth1 src 23.215.17.54 ip rule add from 23.215.3.20 table T1 ip rule add from 23.215.17.54 table T3 ip rule add from 23.215.4.61 table T2 ip route add 23.215.3.20 dev eth0 table T1 ip route add 23.215.4.61 dev eth2 table T1 ip route add 23.215.17.54 dev eth1 table T1 ip route add 127.0.0.0/8 dev lo table T1 ip route add 23.215.3.20 dev eth0 table T2 ip route add 23.215.4.61 dev eth2 table T2 ip route add 23.215.17.54 dev eth1 table T2 ip route add 127.0.0.0/8 dev lo table T2 ip route add 127.0.0.0/8 dev lo table T3 ip route add 23.215.17.54 dev eth1 table T3 ip route add 23.215.4.61 dev eth2 table T3 ip route add 23.215.3.20 dev eth0 table T3 #Load Balancing ip route add default scope global nexthop via 23.215.3.17 dev eth0 weight 40 nexthop via 23.215.4.1 dev eth2 weight 30 nexthop via 23.215.16.1 dev eth1 weight 30 Any help would be great, this is a new procedure for me and it would be nice to get it all sorted out and working. - Jason _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
This didn''t have any effect, however I have made the changes for resources sake. Thanks for the info! On Sun, 2004-08-29 at 10:37, RonSenykoff@edapt.us wrote:> Maybe try changing your weights from 40, 30, 30 to 4, 3, and 3 > respectively in your code listed below. The way the ''balancing'' works > is it creates a bunch of virtual interfaces, one for each number in > the weight, then picks between them. By defining 40, 30, 30 you''re > creating 100 different interfaces... quite a bit to handle. Even if > this doesn''t solve your problem it will save resources. > > ip route add default scope global nexthop via 23.215.3.17 dev eth0 > weight 40 nexthop via 23.215.4.1 dev eth2 weight 30 nexthop via > 23.215.16.1 dev eth1 weight 30 > > to > > ip route add default scope global nexthop via 23.215.3.17 dev eth0 > weight 4 nexthop via 23.215.4.1 dev eth2 weight 3 nexthop via > 23.215.16.1 dev eth1 weight 3 > > HTH > -Ron >_______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Just to add some additional information which I''m not sure on weather or not it will help. If I change the Lines: ip route add 23.215.3.16/28 dev eth0 src 23.215.3.20 table T1> ip route add default via 23.215.3.17 table T1 > ip route add 23.215.4.0/26 dev eth2 src 23.215.4.61 table T2 > ip route add default via 23.215.4.1 table T2 > ip route add 23.215.16.0/21 dev eth1 src 23.215.17.54 table T3 > ip route add default via 23.215.16.1 table T3To: ip route add 23.215.3.16/28 dev eth0 src 23.215.3.20 table T1> ip route add 23.215.4.0/26 dev eth2 src 23.215.4.61 table T2 > ip route add default via 23.215.4.1 table T2 > ip route add 23.215.16.0/21 dev eth1 src 23.215.17.54 table T3 > ip route add default via 23.215.16.1 table T3The connection Balancing correctly between eth1 and eth2 .. but no outgoing traffic for eth0 _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> > ip route add default scope global nexthop via 23.215.3.17 dev eth0 > weight 40 nexthop via 23.215.4.1 dev eth2 weight 30 nexthop via > 23.215.16.1 dev eth1 weight 30 > >Another attempt to use this INFAMOUS multipath routing. Did you at all read any of the earlier discussion ? :-) _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>From what I have read some people have been successful with this. Onesuch discussion was from Robert Kurjata who stated he had accomplished this with four uplink providers. The exact same thing I am attempting. P.S I also apologize if my MailList etiquette is not up to par, this is my first time using such a resource. - Cheers -Jason On Sun, 2004-08-29 at 21:54, Ming-Ching Tiew wrote:> > > > ip route add default scope global nexthop via 23.215.3.17 dev eth0 > > weight 40 nexthop via 23.215.4.1 dev eth2 weight 30 nexthop via > > 23.215.16.1 dev eth1 weight 30 > > > > > > Another attempt to use this INFAMOUS multipath routing. > Did you at all read any of the earlier discussion ? > > :-) > > > > > > > _______________________________________________ > LARTC mailing list / LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/_______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/