All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darshan Purohit <purohitdarshan@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] equal-cost multipath in 2.6.7
Date: Tue, 24 May 2005 19:07:42 +0000	[thread overview]
Message-ID: <5f13657050524120746b4da78@mail.gmail.com> (raw)

I have question about multipath routing. I am running a 2.6.7 kernel (gentoo). 
I have  a route with three nexthops on the same interface. I see a
different nexthop being picked for different destination addresses.
All is fine.

Now if one of the nexthop goes down (arp entry times out and arp
request doesnt get a response), does it remove the nexthop from
contention and only use the remaining two from this point on ?  What
about the flows for which this nexthop was chosen in the recent past.
Would they move to a different nexthop ?

Can anyone please point me to  implementation details about how a
nexthop is chosen and what is the algorithm used in case of multipath
routes and how to fine-tune the behaviour.

Thanks.
Darshan.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2005-05-24 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 19:07 Darshan Purohit [this message]
2005-05-24 21:00 ` [LARTC] equal-cost multipath in 2.6.7 Taylor, Grant

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=5f13657050524120746b4da78@mail.gmail.com \
    --to=purohitdarshan@gmail.com \
    --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.