From: Andrew andrewd@uccsda.org
To: lartc@vger.kernel.org
Subject: [LARTC] A complicated routing scenario (for me at least)
Date: Mon, 13 Nov 2000 22:58:14 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216914@msgid-missing> (raw)
<PRE>Greetings:
I've been pouring over every piece of documentaiton on the subject I can
find, and I've concluded that advanced routing + ipchains is what I
need. It also appears that the people that can answer some of the more
in depth questions I have, read this list.
I'm fairly new to this so please forgive me if I ask stupid questions.
Anyway.
Here is what I'm trying to accomplish in ASCII art:
LAN
| (172...)
|
_/\__/\_ +---+----+ _/\__/\_
/ \ (63...) | | (204...) / \
( Internet )-----------+ Router +----------( Internet )
\_ __ _/ | | \_ __ _/
\/ \/ +----+---+ \/ \/
| 63..
| 204..
|
--+---------------+----------+-- <---single physical
net
| | (i.e. one hub)
| |
+---+---+ 63..1 +---+---+ 63..2
| Linux | 63..4 | Linux | 63..3
+-------+ 204..1 +-------+ 204..2
204..4 204..3
The desired end result is a redundant connection to two dns/mail servers
from the
internet. I'm willing to fight through this, but I have a few specific
question's
for now that I'm hoping someone can answer.
1. From a server's perspective, do incoming packets get responded to on
the same interface they came in on? Does it matter if the interface in
question is an alias?
2. if I tag a packet coming into the router/firwall above with ipchains
for routing purposes, will the tag persist to the reply packets? Or do I
have to tag the reply packets with ipchains from the responding server?
3. In reading the various documentation, I noticed several references to
files in the /etc/iproute2 directory. Related to this directory:
a) is there any documentation on the names and syntax of the various
files other than the source code, and the casual references I've found?
b) I don't currently have this directory in /etc. Is it something I
just create, and does it's existance imply that the kernel will read
configureation data from it on boot?
Incidentally I'm currently using kernel 2.2.17 on my boxes. Since I'm
already going to be meticulously documenting my setup, I'd be willing to
do so in a format that could be posted as a HOWTO or as an example in
someone else's HOWTO, whatever would be most usefull.
Suggestions in this area are much appreciated since I have no experiance
in HOWTO writing. (Plenty of writing experiance, just not howtos)
Anyway, Thanks for the help.
-Andrew
</PRE>
next reply other threads:[~2000-11-13 22:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 22:58 Andrew [this message]
2000-11-14 14:34 ` [LARTC] A complicated routing scenario (for me at least) Arthur
2000-11-14 14:44 ` Wingtung.Leung
2000-11-14 20:15 ` Andrew
2000-11-14 21:47 ` Whit
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-98373938216914@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.