From: Andrew depaan@bibleinfo.com
To: lartc@vger.kernel.org
Subject: [LARTC] Linux 2.4 Redundant Internet Connection HOWTO
Date: Thu, 01 Feb 2001 20:29:59 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416938@msgid-missing> (raw)
<PRE>Hello,
I have just finished writing the howto mentioned above. As promised (See
LARTC archives under subject "A complicated routing scenario..." I am willing
to post it for people to see/use and give me feedback on. However, not
wanting to bog the list I thought I'd post this first and see what I get back.
I don't currently have a place to put it on the web yet, so I can't just
point you to a URL. I'd be willing to post a message to the mailing list with
the howto attached, but I'm not sure how appropriate that would be.
Comments suggestions are welcome. I have the following files available
MSWord document version (185K)
Postscript version (422K)
PDF version (104K)
PS. For an Idea of what the HOWTO contains, here's the TOC:
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
-Andrew
--
Want answers to life's big questions? Visit www.bibleinfo.com.
</PRE>
next reply other threads:[~2001-02-01 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 20:29 Andrew [this message]
2001-02-01 21:09 ` [LARTC] Linux 2.4 Redundant Internet Connection HOWTO bert
2001-02-20 23:20 ` Andrew
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-98373940416938@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.