From: Jerry Amundson <jerry-LARTC@pbs.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Dual T1's and firewalls/Nat, Help?
Date: Fri, 18 Jul 2003 17:13:19 +0000 [thread overview]
Message-ID: <marc-lartc-105854851828052@msgid-missing> (raw)
Hi.
I'm new to these tools, but well versed in Linux and networking, and I
just haven't found out some general stuff by going through the HOWTO's!
We have two (2) Internet T1's (different providers), each connected to
individual routers (one a Cisco, the other an Adtran, if it matters),
which are kept apart from the internal networks by two (2) Cisco PIX
firewall devices. The latter do NAT/PAT, in addition to normal network
protection. One (1) firewall/T1 is currently "primary" as it is the
Default Gateway for everything inside.
My *goal* is to put a Linux router in place as the Default Gateway to
be redundant and load balance across the T1's.
Q1: I'm in the right place, right? :-)
Q2: Assuming I am in the right place, the part I don't understand is
how to fit the Linux router in with the existing firewalls.
In a picture, we have:
----------------------
- DMZ1
ISP1 - R1 -ONet1-Firewall1-|
- INet1 <-> [internal NIC, Default Gateway]
ISP2 - R2 -ONet2-Firewall2-- DMZ2
And what we would like:
-----------------------
- DMZ1
ISP1 - R1 -ONet1-Firewall1-|
- INet1 -| |
| Linux Router | <-> [new Gateway]
ISP2 - R2 -ONet2-Firewall2-- DMZ2 ---| |
I can revisit the HOWTO's, and many fine sites referenced in this list,
but I wanted to make sure I was on the right track...
Please be gentle - I don't even know what the abbreviations tc, htb, or
imq mean, yet!!
Thanks,
jerry
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-07-18 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 17:13 Jerry Amundson [this message]
2003-07-18 18:44 ` [LARTC] Dual T1's and firewalls/Nat, Help? William L. Thomson Jr.
2003-07-19 20:30 ` Stef Coene
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-105854851828052@msgid-missing \
--to=jerry-lartc@pbs.com \
--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.