All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arthur van Leeuwen arthurvl@sci.kun.nl
To: lartc@vger.kernel.org
Subject: [LARTC] load balance/redundancy
Date: Sun, 10 Dec 2000 17:57:47 +0000	[thread overview]
Message-ID: <marc-lartc-98373938217018@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938217013@msgid-missing>

<PRE>On Sun, 10 Dec 2000 <A HREF="mailto:hesselsp@ashaman.dhs.org">hesselsp@ashaman.dhs.org</A> wrote:

&gt;<i> Well, I think I have the redundancy down... In a kludgy way.  Right now I
</I>&gt;<i> have two default routes.
</I>
&gt;<i> route add default gw 24.141.xxx.1
</I>&gt;<i> route add default gw 64.229.xxx.1
</I>
Actually, if I understand the code correctly what you do here is in fact
create a multipath route. A cleaner way to do so is using ip route 2 as
follows:

ip route add default nexthop via 24.141.xxx.1 nexthop via 64.229.xxx.1

This explicitly states that you will be using a multipath route and balances
outgoing routes over the two interfaces.

&gt;<i> I can write a script that if one of connections goes down for x number of
</I>&gt;<i> pings, then remove the route.
</I>
And here's the crux. It would be nice for the kernel to use its idea of
gateway reachability (in the neighbor cache) to automatically ignore an
upstream hop in case it is dead. However, for multipath routes, no
death detection is done on the gateways in the different hops. This is
quite somewhat different from the single default route behaviour 

&gt;<i> Now for the load balancing.
</I>
The kernel balances outgoing routes over the upstream interfaces. Unless all
your packets go to the same address, that should balance your traffic
already. Other than that there's some code based on EQL that will flush the
route cache after every packet, thereby smashing the route-balancing down to
packet-level load balancing. I can't seem to find the URL for that code,
though, unfortunately.

&gt;<i> Can you point me to documentation on iproute?  Other then the Advanced
</I>&gt;<i> Routing HOWTO, unless I am missing something in it.
</I>
<A HREF="http://snafu.freedom.org/linux2.2/iproute-notes.html#doc">http://snafu.freedom.org/linux2.2/iproute-notes.html#doc</A>

There's some more interesting stuff on <A HREF="http://snafu.freedom.org/linux2.2/">http://snafu.freedom.org/linux2.2/</A>
as well. 

Doei, Arthur.

-- 
  /\    / |      <A HREF="mailto:arthurvl@sci.kun.nl">arthurvl@sci.kun.nl</A>      | 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



</PRE>

  parent reply	other threads:[~2000-12-10 17:57 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 [this message]
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

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-98373938217018@msgid-missing \
    --to=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.