Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Kevin White <kwhite@telsource.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Two upstream gateways, only use one unless it fails?
Date: Fri, 06 Oct 2006 04:06:08 +0000	[thread overview]
Message-ID: <4525D630.1040401@telsource.com> (raw)

I'm looking at setting up a system with two upstream Internet routers,
the second to be used only if the first fails.

There's a lot of information on using Julian's patches (the nano
document), and I'm still digesting all of it.  It looks pretty slick,
and I think it will work...but I don't see if I can actually set up
multipath and have the kernel not use the second interface unless it has
to.  It looks like I can only set weight and set up a percentage rule.

Am I missing something?  Can I say "here are two routes, always use
route one unless you can't?"

Thanks,

Kevin

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

                 reply	other threads:[~2006-10-06  4:06 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=4525D630.1040401@telsource.com \
    --to=kwhite@telsource.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