From: dan_c@heavenfalls.org dan_c@heavenfalls.org
To: lartc@vger.kernel.org
Subject: [LARTC] load balance/redundancy
Date: Mon, 11 Dec 2000 09:56:21 +0000 [thread overview]
Message-ID: <marc-lartc-98373938217022@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938217013@msgid-missing>
<PRE>
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
><i> >
</I>><i> > # /sbin/ip route add default nexthop via 24.141.xxx.1 nexthop via
</I>><i> > 64.229.xxx.1
</I>><i> > RTNETLINK answers: Network is unreachable
</I>><i>
</I>><i> You forgot to setup host routes to 64.229.xxx.1 and 24.141.xxx.1 over the
</I>><i> correct interfaces.
</I>><i>
</I>><i> > So instead, I tried:
</I>><i> >
</I>><i> > # /sbin/ip route add default nexthop via 24.141.xxx.1 dev eth0 nexthop via
</I>><i> > 64.229.xxx.1 dev ppp0
</I>><i>
</I>><i> Well, that works as well. No host routes needed. :)
</I>><i>
</I>><i> > # ip route ls
</I>><i> > 64.229.xxx.1 dev ppp0 proto kernel scope link src 64.229.xxx.12
</I>><i> > 24.141.xxx.0/22 dev eth0 proto kernel scope link src 24.141.xxx.89
</I>><i> > 127.0.0.0/8 dev lo scope link
</I>><i> > default
</I>><i> > nexthop dev eth0 weight 1
</I>><i> > nexthop dev ppp0 weight 1
</I>><i>
</I>><i> Ah, yes. You might get problems with the selection of the source address you
</I>><i> come from though. The situation that might occur is a route going over ppp0
</I>><i> using 24.141.xxx.89 as source address. That will probably *not* work.
</I>><i>
</I>><i> > Now this seems to work. Is there anything wrong with this? Can you take
</I>><i> > a guess at why what you suggested didn't work? I think I tried all the
</I>><i> > different permutations with addresses, I think the problem must come from
</I>><i> > the pppoe interface.
</I>><i>
</I>><i> I don't think the problem comes from the pppoe interface. I've set up stuff
</I>><i> like this with ppp over pptp over ethernet links (*silly* ADSL setup), and
</I>><i> that works as well.
</I>><i>
</I>><i> > Now all I have to do is kludge something together for my redundancy, set
</I>><i> > up firewalling, and masqerading.
</I>><i>
</I>><i> Note: you may want to set up policy rules for dealing with packets that
</I>><i> already have a source or destination address. This will let servers running
</I>><i> on your system that bind to 0.0.0.0/0 answer to requests from both links
</I>><i> over the correct link. Browse through the mailinglist archives for some
</I>><i> hints on how to set that up.
</I>><i>
</I>><i> Doei, Arthur.
</I>><i>
</I>><i> --
</I>><i> /\ / | <A HREF="mailto:arthurvl@sci.kun.nl">arthurvl@sci.kun.nl</A> | Work like you don't need the money
</I>><i> /__\ / | A friend is someone with whom | Love like you have never been hurt
</I>><i> / \/__ | you can dare to be yourself | Dance like there's nobody watching
</I>><i>
</I>><i>
</I>><i> _______________________________________________
</I>><i> LARTC mailing list / <A HREF="mailto:LARTC@mailman.ds9a.nl">LARTC@mailman.ds9a.nl</A>
</I>><i> <A HREF="http://mailman.ds9a.nl/mailman/listinfo/lartc">http://mailman.ds9a.nl/mailman/listinfo/lartc</A> HOWTO: <A HREF="http://ds9a.nl/2.4Routing/">http://ds9a.nl/2.4Routing/</A>
</I>
</PRE>
prev parent reply other threads:[~2000-12-11 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-10 5:22 [LARTC] load balance/redundancy Paul
2000-12-10 16:30 ` Arthur
2000-12-10 17:32 ` hesselsp
2000-12-10 17:57 ` Arthur
2000-12-10 23:50 ` Paul
2000-12-11 0:11 ` hesselsp
2000-12-11 8:00 ` Arthur
2000-12-11 9:56 ` dan_c [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-98373938217022@msgid-missing \
--to=dan_c@heavenfalls.org \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.