From: Warren Flemmer warren@netlab.co.za
To: lartc@vger.kernel.org
Subject: [LARTC] A complicated routing scenario (for me at least)
Date: Wed, 15 Nov 2000 14:57:23 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216922@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216914@msgid-missing>
<PRE>Greetings
I am new to iproute2 and therefore would not try to give a direct answer to
any of your questions. I have, however, been working on what seems to me to
be a similar problem and will offer it here in case it assists.
I two have two links to the internet though different isps. The requirements
were that users on the lan would be as oblivious as possible to any one link
going down.
The solution I came up with involved two new linux boxes. Both using iproute
and one using masq (nat with 2.4 when released). One box was placed between
the two isps with source routing and a third network card linking to the
dns,www etc (I call it a crossrouter). The second box also links the two
isps and uses source routing and masq to offer redundancy (redundancy box).
An attempt at text art may help
isp1 +redundancy box+ isp2
|<i> | |
</I>|<i>
</I>+---------------------+ +---------------------+
| |
+ Crossrouter +
|
---+---------+---------------+----------------------------------Lan
www dns etc
I made may attempts to use one box instead of two without any luck. I had
bad results with marking that would have made a single box solution
possible. The result was the two boxes. On the routers to the isp I have a
second default route to the redundancy box with a higher matrix. If one link
fails the data is routed to the redundancy box where it is masq on an ip
(one assigned by the isp with the good link) address and sent out through
the other isp. Every test I have done is showing the solution to work but it
has not been fully deployed yet.
I would imagine that this type of solution would be worth using is you link
to two different isps and BGP is not available. I intend doubling up on the
crossrouter as it will become a single point of failure.
If anyone knows of a better solution I would be interested to know.
Hope this helps
Regards
Warren
</PRE>
next prev parent reply other threads:[~2000-11-15 14:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 22:58 [LARTC] A complicated routing scenario (for me at least) Andrew
2000-11-14 14:34 ` 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 [this message]
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-98373938216922@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.