Firewal advice reqd., Kerio 2.1.5 or 4.0.16..... TIA

  • Thread starter Thread starter JustMe
  • Start date Start date
J

JustMe

Hi:

Which would be a better decision... to install Kerio 2.1.5 (Last freeware
version) or to install Kerio 4.0.16 and run it in "freeware mode"

TIA
 
lunedì 10/mag/2004 _JustMe_ ha scritto:
Hi:

Which would be a better decision... to install Kerio 2.1.5 (Last freeware
version) or to install Kerio 4.0.16 and run it in "freeware mode"

TIA
Click to expand...

Kerio 2.1.5 without any doubt.
Google for it in this NG and you'll see yourself :)
 
JustMe said:
Which would be a better decision... to install Kerio 2.1.5 (Last freeware
version) or to install Kerio 4.0.16 and run it in "freeware mode"
Click to expand...

Install Sygate Personal Firewall, Kerio has some leeks.
 
Hi:

Which would be a better decision... to install Kerio 2.1.5 (Last freeware
version) or to install Kerio 4.0.16 and run it in "freeware mode"
Click to expand...

Go for 2.1.5. It works very well. I tried the later version and had
problems with it, as have others.
 
Hi:

Which would be a better decision... to install Kerio 2.1.5 (Last freeware
version) or to install Kerio 4.0.16 and run it in "freeware mode"
Click to expand...

Up until a few days ago, I would have said 2.1.5 without a doubt. But
I've been having some problems with 2.1.5 which has made me switch to
4.0.16 recently. For some reason in 2.1.5, packets are getting in and
generating outbound icmp type 3 to various IPs, none of which are my dns
servers. I've tried various rule sets, some by "experts" and the
problem remains.. Don't know why either, but I no longer trust 2.1.5.
This problem does not happen with 4.xx (using my 2.1.5 rule set) or with
Sygate 5.5 either. So something's amiss in 2.1.5.
 
jo said:
Explain?
Click to expand...

I can't explain it.
I only know that one morning I kept getting these messages from Sygate that
a Port Scan was allowed.
I checked the security log and one company whose name I can not recall, had
made 31 'Port Scans' on my computer.
I removed Sygate.
 
For some reason in 2.1.5, packets are getting in and
generating outbound icmp type 3 to various IPs, none of which are my dns
servers.
Click to expand...

You are only assuming that "packets are getting in" and causing this. Odd
that many thousnads of people are still using Kerio 2.1.5, many of them top
line security experts, and nobody else either has this trouble or sees
nothing wrong with it.

Says you.
 
You are only assuming that "packets are getting in" and causing this. Odd
that many thousnads of people are still using Kerio 2.1.5, many of them top
line security experts, and nobody else either has this trouble or sees
nothing wrong with it.


Says you.
Click to expand...

Yep. It IS odd.. I've talked to other people who apparently don't have
this problem. I have no idea what's wrong, and in fact I gave up for
now and am using Kerio 4.0.16 instead, which doesn't have this problem.
Same rule set and everything. 4.xx is ok, but I miss the logging that
2.1.5 has.

Anyway, we all have to use what works for us, right?
 
Kerodo said:
Up until a few days ago, I would have said 2.1.5 without a doubt. But
I've been having some problems with 2.1.5 which has made me switch to
4.0.16 recently. For some reason in 2.1.5, packets are getting in and
generating outbound icmp type 3 to various IPs, none of which are my dns
servers. I've tried various rule sets, some by "experts" and the
problem remains.. Don't know why either, but I no longer trust 2.1.5.
This problem does not happen with 4.xx (using my 2.1.5 rule set) or with
Sygate 5.5 either. So something's amiss in 2.1.5.
Click to expand...

Have you tried using a packet sniffer to see what packets are getting
in and from where? I'm using Kerio 2.1.5 with no problems.

Also, have you tried adding a "Deny All" rule at the bottom?
 
[email protected]# said:
Have you tried using a packet sniffer to see what packets are getting
in and from where? I'm using Kerio 2.1.5 with no problems.

Also, have you tried adding a "Deny All" rule at the bottom?
Click to expand...

Nope, I haven't tried using a packet sniffer.. I'm not familiar with
them. I'll have to do a little research and try that.

I do have a Deny All Inbound rule at the bottom, yes.

Thanks for the suggestion...
 
Back
Top