From: Andrew depaan@bibleinfo.com
To: lartc@vger.kernel.org
Subject: [LARTC] Linux 2.4 Redundant Internet Connection HOWTO
Date: Tue, 20 Feb 2001 23:20:44 +0000 [thread overview]
Message-ID: <marc-lartc-98373940417041@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416938@msgid-missing>
<PRE>Hello all,
Sorry for the long delay on getting my stuff up somewhere. I'm hoping to have
it up on the LDP as a mini-HOWTO one of these days, and Bert Hubert from the
list has kindly offered to host my files as well.
But until all this get's ironed out, I'd like for people to be able to
download the files, and send me comments about it.
Thanks to Daniel Jay, this is possible. You can download the PS and PDF
versions of my HOWTO at the following urls:
<A HREF="http://red-int.nashlink.net/redundant_connection-HOWTO.ps">http://red-int.nashlink.net/redundant_connection-HOWTO.ps</A>
<A HREF="http://red-int.nashlink.net/redundant_connection-HOWTO.pdf">http://red-int.nashlink.net/redundant_connection-HOWTO.pdf</A>
Sorry there's no web page but this was quick and dirty.
Just by way of reference, here's the TOC again.
-Andrew
Contents:
1. Introduction
1.1 Disclaimer & license
1.2 Prior knowledge
1.3 Required software
2. Miscellany
2.1 Topologies
2.2 Kernel packet flow
3. Getting started
3.1 Router box preparation
3.2 Building & installing a proper kernel
3.3 Network subsystem configuration
3.4 Rules and routes-single router
3.5 Rules and routes-two routers
3.6 DNS wizardry
3.7 WARNING
4. Testing
4.1 Single router instructions
4.2 Dual router instructions
5. Acknowledgements
6. Appendix A - scripts for single router example
7. Appendix B - scripts for dual router example
</PRE>
prev parent reply other threads:[~2001-02-20 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 20:29 [LARTC] Linux 2.4 Redundant Internet Connection HOWTO Andrew
2001-02-01 21:09 ` bert
2001-02-20 23:20 ` Andrew [this message]
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-98373940417041@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.