[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::seal

Title:	SEAL

Moderator:	GALVIA::SMITH

Created:	Mon Mar 21 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1989
Total number of notes:	8209

1935.0. "questions on Unix Firewall V1.0" by NQOS01::16.72.96.24::Cindy () Fri Apr 25 1997 17:26

What is the "status" of the Firewall for Unix product? I have a customer who 
has one and it is currently not being implemented.  They would like to put it 
in place as an Intranet firewall between 2 existing ethernet segments.  Are 
there any software issues why this would not be a good idea?  (Like does it 
support intranet configurations and are there some potential performance 
issues?).  It is currently running on an Alphastation 200.  If we have not 
already dropped support of this product, is it going to be dropped in the near 
future?

Thanks

T.R Title User Personal
Name Date Lines

1935.1 CHEFS::16.37.11.61::PITT Gone with the winsock ... Mon May 12 1997 10:32 30

T.R	Title	User	Personal Name	Date	Lines
1935.1		CHEFS::16.37.11.61::PITT	Gone with the winsock ...	`Mon May 12 1997 10:32`	30
	This is a strange question. The product you are referring to has been updated to DFW V2.0, and then to AFWU V2.1, and then the relevant Engineering effort was placed into the subsidiary called AltaVista Software Inc, and now the product is being updated to AFWU V3.0. Meanwhile, that version ran on V3.2C (and D?) of Digital UNIX, and we're currently on V4.0B ... I also know from experience that the support for the firewall products has always been patchy - for example, MCS in the UK don't support AFWBSDI at all, because they don't support BSDI UNIX! Given all this, I would tell you customer that there is no way they are going to get effective support of any kind for that version. The product is more than capable of handling Intranet configurations, _IF_ the applications that have to talk across it can be handled suitably. This is not very easy to determine in many cases. I would suggest that your customer buy a bit of firewall design time from a firewall consultant, to determine what is appropriate, and to implement it. They ought, I think, to be able to buy an upgrade license to AFWU V3.0, but you'll need to clarify that with the AltaVista folks ... T

This is a strange question.  The product you are 
referring to has been updated to DFW V2.0, and then
to AFWU V2.1, and then the relevant Engineering effort
was placed into the subsidiary called AltaVista Software
Inc, and now the product is being updated to AFWU V3.0.

Meanwhile, that version ran on V3.2C (and D?) of Digital
UNIX, and we're currently on V4.0B ...

I also know from experience that the support for the firewall
products has always been patchy - for example, MCS in the UK
don't support AFWBSDI at all, because they don't support BSDI
UNIX!

Given all this, I would tell you customer that there is no
way they are going to get effective support of any kind
for that version.

The product is more than capable of handling Intranet
configurations, _IF_ the applications that have to talk
across it can be handled suitably.  This is not very easy
to determine in many cases.

I would suggest that your customer buy a bit of firewall design
time from a firewall consultant, to determine what is
appropriate, and to implement it.  They ought, I think, to be
able to buy an upgrade license to AFWU V3.0, but you'll need
to clarify that with the AltaVista folks ...

T