Re: Information on Raptor

[dl () WILLOW NET (Daniel Liebster)]

I  used Raptor for over a year, and never had the problems you mentioned. I
ran it under NT, on a self built P2-266/256MB RAM. Network topology had a T1
going out(supporting several ISDN and cable modem VPN clients), and 3
internal 100 BT networks. It Firewalled web, mail, and ftp servers from the
inside and out, and provided DNS. We would max out the CPU occasionally, but
considering all the rules we had, heavy traffic(100MB-2GB files), and that
it was NT underneath it all, that's not too surprising.

Now, while Raptor never spontaneously re/misconfigured itself, we did have
the some problems with the box at one time. The symptoms sounded like the
ones Jeff described in his email. We found the problem to be an admin who
was looking to get up to speed on Raptor. He had inadvertently saved changes
to the config he made during his voyages of discovery through the Raptor
GUI. Other than this episode, the box just ran.

Dan Liebster

----- Original Message -----
From: "CL: Nelson, Jeff" <JNelson () CMCCONTROLS COM>
To: <VULN-DEV () SECURITYFOCUS COM>
Sent: Thursday, February 24, 2000 9:26 AM
Subject: Re: Information on Raptor

> We never had any consultants tell us about the issues with Raptor. We
simply
> experienced them. We still experienced them after Raptor's technical
support
> people worked with us on a complete new install. Raptor would things like
> stop listening on port 25. It would also 'forget' the various rules we had
> in place. No reason, no notification. Of course, we were running it under
> NT. These problems were what caused us to take the hit and make the
> investment in a PIX-520. Now THERE is a firewall. We have had no problems
> and superior protection.
>
> Regards,
>
> Jeff
>
> :::::::::::::::::::::::
> Jeffrey L. Nelson
> Network Manager
> Cleveland Motion Controls