Re: Kerio PF 4.2

From: \ (dvader_at_deathstar.mil)
Date: 08/30/03 

Date: Sat, 30 Aug 2003 11:07:41 -0400

>Why is 2.15 doomed ? It works, you can tell it what to do and it will
>do it.

>Sure it may not be further developed, but surely it will still work ?

Yes, it will continue to work as long as systems and protocols stay the same,
but they won't. Eventually, some change in the O.S. interface or the internet
protocol will be incompatible with KPF 2.1.5 as it is. That's what happened to
AtGuard.

>Is Atguard free ? Why do you prefer it ? I ask as I use sygate, but
>still don't feel that I understand why it works- can't see the rules
>so easily

It is, now, because it is no longer available, except from somebody that already
has it. It used to be around $40, I think. It hasn't been made or updated since
1999. WRQ, the original designer, sold the rights to Symantec. That became the
kernel for NPF, but any resemblance today is purely coincidental. The AtGuard
interface looks a lot like Kerio, a basic, rule based firewall, which is why I
was looking to Kerio for a replacement.

AtGuard is not fully compatible with XP. As I said, I don't have XP, so I can
only go by what I have been told. The firewall still works, but the logging
doesn't. My latest concern has been SP4 for W2K. A lot of people have had
various problems with AtGuard after installing SP4. Similar problems appeared
for early builds of the Symantec NPF, so it seems to be a real situation. The
difference is that Symantec supplied a patch to fix their product. There is no
patch for AtGuard. So far, I haven't had any problems with AtGuard and SP4, but
as far as I know, I am the only one on the planet who hasn't.

Anyway, this underlines what I said about "doomed to extinction." AtGuard is
still my favorite firewall, but the rest of the World is growing away from it.
The same thing will happen with Kerio 2.1.5 if it is no longer kept updated. 

-- 
Dave "Crash" Dummy - A weapon of mass destruction
crash@gpick.com
http://lists.gpick.com