From: Gerry Creager N5JXS <gerry@cs.tamu.edu>
To: lartc@vger.kernel.org
Subject: [LARTC] Convoluted routing problem
Date: Tue, 10 Jul 2001 12:26:21 +0000 [thread overview]
Message-ID: <marc-lartc-99476812923601@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1771 bytes --]
Apologies in advance if I've offended by including a graphic, but the
network's not real straightforward, and I've spent the better part of a
year travelling back and forth ascertaining that this appears to be
"reality." The documentation, such as it is, doesn't look much like
this but the network _works_ like this.
I've a network that I need to add some multihome capability to, but I'm
at a loss as to how to do it.
Currently, the ISPs labelled ESC6, ESC6 and GSC are active, using T-1s
(or fractional T-1s) to provide connectivity. We've recently lit up a
DS-2, to Gigapop, and want to provide destination-based (AS-based)
services to Internet-2 for the network via the DS-2 connection. Only
Internet-2, at this point, although the schools may want to have us help
them get better regular Internet services later...
All 5 entities have independent, single, static IP addresses for their
Proxy/NAT boxes. None of the existing routers are capable of BGP or
OSPF at this point.
All entities do NAT for multiple subnets within their proxy boxes. Some
of the proxys are Linux w/ N2H2, some use Microsoft Proxt, and one uses
Linux/squid and Apache as a web proxy. It's unlikely that the N2H2 or
Microsoft Proxy boxes will be changed.
I've looked at this for some time. I bounced it upstairs and we spent 4
hours yesterday pounding on this, with some of the best networking minds
I have directly available to pick.
If anyone's got suggestions, I'd love to hear them, either on or
off-list.
TIA,
gerry
--
Gerry Creager -- gerry@cs.tamu.edu
Network Engineering |Research focusing on
Academy for Advanced Telecommunications |Satellite Geodesy and
and Learning Technologies |Geodetic Control
Texas A&M University 979.458.4020 (Phone) -- 979.847.8578 (Fax)
[-- Attachment #2: RESNET-20010704.dia --]
[-- Type: application/octet-stream, Size: 6402 bytes --]
reply other threads:[~2001-07-10 12:26 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-99476812923601@msgid-missing \
--to=gerry@cs.tamu.edu \
--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.