Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Gobbledegeek <gobbledegeek@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] multipath feature
Date: Thu, 22 Sep 2005 07:53:56 +0000	[thread overview]
Message-ID: <463aea5705092200533676ccaf@mail.gmail.com> (raw)

Hello
      Will someonekindly update me on whether julians's patch is now
a standard feature on the linux kernel release? Is there a decision to
provide the same feature but re-worked in some way  (i.e out-of
the-box dead gateway detection for example) in a future release.

Or do I still need to patch the latest kernel release, and do all the
"stuff" as explained in the iproute2 lartc how-to or nano how-to or
dgd usage doc?

Solaris 10 has this multipath feature built-n you know? Why not linux?

--
Nonchalantly yours
GobbledeGeek
[Every thing but Gobbledegook.. !!]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

                 reply	other threads:[~2005-09-22  7:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=463aea5705092200533676ccaf@mail.gmail.com \
    --to=gobbledegeek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox