From: "Daniel Horth" <s042@euroluce.com.au>
To: lartc@vger.kernel.org
Subject: [LARTC] ADSL with PPP failover
Date: Wed, 08 Oct 2003 04:08:01 +0000 [thread overview]
Message-ID: <marc-lartc-106558603601181@msgid-missing> (raw)
Hi - I've been looking around for simple answers to this for a while now,
but haven't been able to find any HOW-TO type documentation. I am
administering a site with a remote location connected primarily via a cipe
tunnel over a SHDSL connection. We also have a direct PSTN connection
between the sites. Seeing as phone calls here are not timed I plan to keep
the PSTN connection alive even when the cipe tunel is active. I am looking
for information as to the best way to set up this network, so that if the
cipe connection goes down all traffic is automatically routed over the ppp
connection, and when the cipe connection comes back up the traffic is once
again routed via the cipe connection.
We currently only have one remote location to worry about, but may soon be
expanding to multiple sites, with multiple links.
I originally thought that I'd be setting this up using weighting in the
routing table, but now believe that methodology is out of date even if it
would work - more recently I have been thinking that this sort of failover
setup would best be implemented using RIP (or is that out of date too?). I
was hoping that someone could tell me if I was headed in the right direction
before I set out reconfiguring the routing on all our servers. I'd also be
grateful for any pointers towards relevant reading or HOW-TOs that relate.
Using Linux 2.4 (Redhat 9)
Thanks in advance!
- Dan.
__________________________________
Euroluce Lighting Australia PTY LTD
92-94 Tennyson Road, Mortlake, NSW 2137
Ph: (02) 9743 6099 Fx: (02) 9743 6406
http://www.euroluce.com.au/
The contents of this email are confidential. If you are not, or believe you
may not be, the intended recipient of this email, please let us know by
reply and then delete it from your system. You should not copy the message
or disclose its contents to anyone. No warranty or other assurance is given
by us that this email is free of any virus or any other defect or error.
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of the company. If verification is
required please request a hard-copy version.
Scanned by Inflex - Queries to: postmaster@euroluce.com.au
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-10-08 4:08 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=marc-lartc-106558603601181@msgid-missing \
--to=s042@euroluce.com.au \
--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.