From: N N Ashok <nalkunda@cse.msu.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] default route
Date: Fri, 31 Oct 2003 00:43:25 +0000 [thread overview]
Message-ID: <marc-lartc-106756224522705@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106749406611702@msgid-missing>
On Thursday 30 October 2003 02:52 am, Vadiraj C S scrawled:
> On Thu, 30 Oct 2003, Damion de Soto wrote:
> > getting lost. anyone comment on this ?
> >
> > If you use the ip route tool to created multiple weighted or equalized
> > default routes, you then use source-based routing to make sure that the
> > traffic goes back out the same route it came in on.
> > (unless you're trying to be tricky with asymetrical routing)
>
> I tried this, the routes get cached so most of the time the packets
> leave from the route they came in, but you can have two routes and
> there is no packet loss.
>
> Vadiraj C S
>
hi,
Having multiple equal cost routes just ensures that the traffic is balanced
per-route, i.e. every time a route is looked up in the FIB table, the
load-balancing comes into picture. but once a route has been established for
a destination, it is cached and all packets to that destination go via that
route. However, if you install the nano patch
(http://www.ssi.bg/~ja/nano.txt), the the load-balancing is done on a
per-packet basis. so for every packet, leaving the system (either forwarded
or output), the FIB table is consulted and the packets are balanced on the
multiple equal-cost paths provided you have 'equalize' keyword for that
multiple equal-cost route.
current i am actually implementing load-balancing (outgoing) on a per-session
and current-bandwidth-usage basis.
hope that helps.
ashok
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
--
-----------------------------------------------------------------------------
N N Ashok
Ph: 408-644-3646 (c)
517-353-4633 (ELANS Lab)
517-355-1789 (ERL Lab)
-----------------------------------------------------------------------------
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-10-31 0:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 5:56 [LARTC] default route Payal Rathod
2003-10-30 6:29 ` Damion de Soto
2003-10-30 7:25 ` Payal Rathod
2003-10-30 7:49 ` Vadiraj C S
2003-10-30 7:54 ` Vadiraj C S
2003-10-30 8:08 ` Vadiraj C S
2003-10-30 8:40 ` Payal Rathod
2003-10-31 0:43 ` N N Ashok [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-106756224522705@msgid-missing \
--to=nalkunda@cse.msu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox