From: Whit whit@transpect.com
To: lartc@vger.kernel.org
Subject: [LARTC] A complicated routing scenario (for me at least)
Date: Tue, 14 Nov 2000 21:47:28 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216918@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216914@msgid-missing>
<PRE>Andrew,
I'm awfully glad you're asking these questions, since I'm contemplating a
similar setup and am not yet to that wonderful place where this presently
obscure new technology resolves into clarity. So I'll be trying to follow
along closely as you work out your scheme.
One question I have, in addition to those you're asking, is whether iproute2
in itself is adequate to handle fallover routing when one of the outside
links goes down - that is, can it just be set up with lower priority rules
to route the other way, or does something like mon
(<A HREF="http://www.kernel.org/software/mon/">http://www.kernel.org/software/mon/</A>) need to be set up to actively change
the routing tables when an outside line goes down?
\/\/ I-I I T
Blauvelt
<A HREF="mailto:whit@transpect.com">whit@transpect.com</A>
</PRE>
next prev parent reply other threads:[~2000-11-14 21:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 22:58 [LARTC] A complicated routing scenario (for me at least) Andrew
2000-11-14 14:34 ` Arthur
2000-11-14 14:44 ` Wingtung.Leung
2000-11-14 20:15 ` Andrew
2000-11-14 21:47 ` Whit [this message]
2000-11-14 23:10 ` Wingtung.Leung
2000-11-15 10:49 ` Arthur
2000-11-15 11:27 ` Arthur
2000-11-15 14:57 ` Warren
2000-11-15 19:20 ` Andrew
2000-11-15 19:30 ` Arthur
2000-11-15 20:11 ` Andrew
2000-11-17 1:07 ` Andrew
2000-11-17 12:11 ` Mike
2000-11-17 12:24 ` Mike
2000-11-17 13:00 ` Arthur
2000-11-17 21:25 ` Mike
2000-11-18 16:28 ` Warren
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-98373938216918@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.