>Return-Path: bhowell @
snlnet .
com
>From: bhowell @
snlnet .
com
>Date: Fri, 11 Oct 1996 14:28:36 -0400
>To: kfrisco <kfrisco @
shrike .
depaul .
edu>
>Subject: Re: <no subject>
>
>Content-Type: text/plain; charset=US-ASCII; name="RFC822 message headers"
>Content-Transfer-Encoding: 7bit
>Content-Description: cc:Mail note part
>
>Received: from relay1.UU.NET by snlmail.snlnet.com with SMTP
> (IMA Internet Exchange 1.04b) id 25e8d8f0; Fri, 11 Oct 96 14:10:23 -0400
>Received: from miles.greatcircle.com by relay1.UU.NET with ESMTP
> (peer crosschecked as: miles.greatcircle.com [198.102.244.34])
> id QQbkzo20677; Fri, 11 Oct 1996 14:01:11 -0400 (EDT)
>Received: (majordom @
localhost) by miles.greatcircle.com
(8.7.1-lists/Lists-960417
>-1) id JAA08622 for firewalls-outgoing; Fri, 11 Oct 1996 09:13:29 -0700 (PDT)
>Received: from shrike.depaul.edu ([140.192.1.10]) by miles.greatcircle.com
(8.7.4
>/Miles-960830-1) with SMTP id JAA08592 for <firewalls @
greatcircle .
com>;
Fri, 11 O
>ct 1996 09:13:04 -0700 (PDT)
>Received: from dept14.ac-sia.depaul.edu (dept14.ac-sia.depaul.edu
[140.192.94.14]
>) by shrike.depaul.edu (8.6.10/8.5) with SMTP id LAA26601; Fri, 11 Oct 1996
11:11
>:41 -0500
>Date: Fri, 11 Oct 1996 11:11:41 -0500
>Message-Id: <199610111611 .
LAA26601 @
shrike .
depaul .
edu>
>X-Sender: kfrisco @
shrike .
depaul .
edu
>X-Mailer: Windows Eudora Light Version 1.5.2
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>To: firewalls @
greatcircle .
com
>From: kfrisco <kfrisco @
shrike .
depaul .
edu>
>Sender: firewalls-owner @
GreatCircle .
COM
>Precedence: bulk
>Content-Type: text/plain; charset=US-ASCII
>Content-Transfer-Encoding: 7bit
>Content-Description: cc:Mail note part
>
> We went with the PIX because it is fairly inexpensive and very easy to
> configure. BUT, if you have no experience with Cisco products or are
> not a TCP/IP super expert, make sure you get the support contract for
> the first year. It is expensive, but Cisco help is great. The manual
> provided with the pix is a 40 page command reference guide. No other
> help other than a few basic examples is included.
>
> The PIX "box" provides NAT so you will need your ISP to supply a pool
> of "real" IP addresses. These get mapped to your internal network as
> needed. We went with the PIX 32 as we do not forsee a need for more
> than 32 external connections through our firewall. The command syntax
> is similar to the Cisco IOS (command line) structure, but different
> enough to cause confusion if you know IOS. No GUI interface and no
> DHCP support if you are using NT.
>
>
>______________________________ Reply Separator
_________________________________
>Subject: <no subject>
>Author: kfrisco <kfrisco @
shrike .
depaul .
edu> at Internet
>Date: 10/11/96 11:11 AM
>
>
>Am just setting up my internet connection and am deciding on a firewall.
>Does anyone have any comments or advice regarding Gauntlet and Cisco PIX?
>
|
|
