From mboxrd@z Thu Jan 1 00:00:00 1970 From: dan_c@heavenfalls.org dan_c@heavenfalls.org Date: Mon, 11 Dec 2000 09:56:21 +0000 Subject: [LARTC] load balance/redundancy Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org
Be attentive : you don't use 24.141.xxx.1 -> xxx should be a number and the "24.141.xxx.1" should be the gateway you're using with the 24.141. ip adress (.videotron.ca?)
and the 64.226.xxx.1 should be the gw your 64.226. ip adress uses (pacbell.net ? :)))) )

Best Regards
   Dan Caescu

> > 
> > # /sbin/ip route add default nexthop via 24.141.xxx.1 nexthop via
> > 64.229.xxx.1
> > RTNETLINK answers: Network is unreachable
> 
> You forgot to setup host routes to 64.229.xxx.1 and 24.141.xxx.1 over the 
> correct interfaces.
> 
> > So instead, I tried:
> > 
> > # /sbin/ip route add default nexthop via 24.141.xxx.1 dev eth0 nexthop via
> > 64.229.xxx.1 dev ppp0
> 
> Well, that works as well. No host routes needed. :)
> 
> > # ip route ls
> > 64.229.xxx.1 dev ppp0  proto kernel  scope link  src 64.229.xxx.12
> > 24.141.xxx.0/22 dev eth0  proto kernel  scope link  src 24.141.xxx.89
> > 127.0.0.0/8 dev lo  scope link
> > default
> >         nexthop dev eth0 weight 1
> >         nexthop dev ppp0 weight 1
> 
> Ah, yes. You might get problems with the selection of the source address you
> come from though. The situation that might occur is a route going over ppp0
> using 24.141.xxx.89 as source address. That will probably *not* work.
> 
> > Now this seems to work.  Is there anything wrong with this?  Can you take
> > a guess at why what you suggested didn't work?  I think I tried all the
> > different permutations with addresses, I think the problem must come from
> > the pppoe interface.
> 
> I don't think the problem comes from the pppoe interface. I've set up stuff
> like this with ppp over pptp over ethernet links (*silly* ADSL setup), and
> that works as well.
> 
> > Now all I have to do is kludge something together for my redundancy, set
> > up firewalling, and masqerading.
> 
> Note: you may want to set up policy rules for dealing with packets that
> already have a source or destination address. This will let servers running
> on your system that bind to 0.0.0.0/0 answer to requests from both links
> over the correct link. Browse through the mailinglist archives for some
> hints on how to set that up.
> 
> Doei, Arthur.
> 
> -- 
>   /\    / |      arthurvl@sci.kun.nl      | Work like you don't need the money
>  /__\  /  | A friend is someone with whom | Love like you have never been hurt
> /    \/__ | you can dare to be yourself   | Dance like there's nobody watching
> 
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/