From: Guy Van Den Bergh guy.vandenbergh@bigfoot.com
To: lartc@vger.kernel.org
Subject: [LARTC] Backup Route
Date: Fri, 17 Nov 2000 04:33:38 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216935@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216930@msgid-missing>
<PRE>For configuring a backup route, it shouldn't be that difficult.
You should configure the preferred route (the radio link) statically,
with the default metric,
and for the backup route (ADSL link), configure it (also statically)
with a higher metric.
This way traffic will go along the preferred route, as long as the link
is up.
When the link fails, the route with the higher metric should take over.
The routing algorithm will always take a (valid) route with the lowest
metric.
But indeed, you should read the iproute2 docs,
and test the configuration you've chosen.
If you want to do load balancing and traffic filtering, all the others
(iptables/ipchains and
the advanced routing howto )come into the picture. But for mere backup
routes, playing with metrics will do.
Regards, Guy
Andrew wrote:
><i>
</I>><i> "Michel A. S. Pereira - KIDMumU[InLove]" wrote:
</I>><i> >
</I>><i> > Hi there.
</I>><i> >
</I>><i> > I've two Internet connections at the same box, one connection is
</I>><i> > made through ADSL, and another is made with a Radio-Link (WaveLAN
</I>><i> > IE822).
</I>><i> > I wan't to do a backup connection with the ADSL link.
</I>><i> > With what tools I can do this?
</I>><i> > ipchains, iptables, a third party tool?
</I>><i> >
</I>><i> I'm in the middle of doing something very similar. I don't know how often they
</I>><i> update the archives on this list but the subject on the thread for what I'm
</I>><i> working on
</I>><i> is [a complicated routing scenario (for me at least)]
</I>><i>
</I>><i> Basically you'll have to compile the advanced routing options into the kernel
</I>><i> allong with ipchains, then install the iproute2 tools. Then you'll have to
</I>><i> configure your box properly using the advanced routing tools and ipchains for
</I>><i> the redundant routes. It's way too complicated to explain it all in one email,
</I>><i> so your best bet is to look in the archives on this list.
</I>><i>
</I>><i> Probably your single best source of information in the way of docs is the
</I>><i> command reference doc for the "ip" command (comes in the iproute2 package). If
</I>><i> you read and understand this doc, you'll be well on your way to doing what you
</I>><i> want to do. You can also read the ipchains howto, the advanced routing howto,
</I>><i> and the ip-masquerading howto.
</I>><i>
</I>><i> When I get it all done, I'm thinking of writing a howto on the subject, we'll
</I>><i> see...
</I>><i>
</I>><i> -Andrew
</I>><i>
</I>><i> _______________________________________________
</I>><i> LARTC mailing list / <A HREF="mailto:LARTC@mailman.ds9a.nl">LARTC@mailman.ds9a.nl</A>
</I>><i> <A HREF="http://mailman.ds9a.nl/mailman/listinfo/lartc">http://mailman.ds9a.nl/mailman/listinfo/lartc</A> HOWTO: <A HREF="http://ds9a.nl/2.4Routing/">http://ds9a.nl/2.4Routing/</A>
</I>
</PRE>
next prev parent reply other threads:[~2000-11-17 4:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 21:10 [LARTC] Backup Route Michel
2000-11-16 22:49 ` Andrew
2000-11-17 1:34 ` bert
2000-11-17 4:33 ` Guy [this message]
2000-11-17 10:41 ` Mike
2000-11-17 11:03 ` Emmanuel
2000-11-17 11:56 ` Mike
2003-03-19 15:19 ` [LARTC] backup route Marijus Spakovskis
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-98373938216935@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.