Filseclab latest truly excellent

Filseclab never went over 15mb on my system and peak CPU usage on my dual CPU machines was around 3%.

 

I checked my system a short while ago and RAM usage for Filseclab was 12.7 MB with 2% CPU utilization.

 

I personaly don't like that a firewall use CPU when I don't use any bandwidth, and Filseclab use...

So this is the first reason to wait for another version with this issue fixed...

 

Sygate does this also.. If it is only a 2-3% cpu usage then I don't see much harm in that..

 

When I tried it, was between 2-20%...

 

Yep, anything over 2 or 3 is not good.. especially when it's just idling. I'd use something else or wait for an update like you say...

 

At least, I don't have this issue with Outpost Pro or NetVeda...

 

I have tried many firewalls and only had a cpu% issue with Sygate so far. Only one. All others were acceptable...

 

I install it on another computer, test it on Sygate and Shields UP!!.

It fails on Shields UP!! on:

File Sharing:
- A Next-Generation PRIVACY THREAT is present!

Common Ports:
- The port 0 and 80 are closed instead of shield...

Can you now a way to fix this with Filseclab?

Thanks

 

What is your OS (XP,98,2000 ?)
I have XP SP2 and:
I have only port 110 closed. The other ports are stealth.

Concerning the Next-Generation PRIVACY THREAT, it's new on Shield Up!
And when you read the comment, it appears there is no real solution at the moment.
I will try with another computer and other firewalls to see is Filseclab is guilty

 

A review of Filseclab:

http://redhatcoc.blogspot.com/2005/08/filseclab-personal-firewall-review.html

Another one by the same tester:

http://redhatcoc.blogspot.com/2005/09/filseclab-another-go.html

 

WinXP SP2 Pro.

I tried it Outpost Pro and didn't have the problems that I reported...

 

Key-U,

nice info...

thanks

 

About teh test,his first peeve was that it doesnt pass leak tests like Tooleaky, show me one free firewall that does, it never claimed to be a component control firewall like ZAP so one should never look at it in that sense, there are additional free apps like Antihook when combined with Filseclab can achieve the same thing the paid component control firewalls claim to do.

I always got stealth on my Win2K machine, on dial up and GPRS.

 

I stopped using Filseclab because you can't specify more than one port. (Unlike Kerio's List Ports feature).

I'm currently using LnS, and it's working very good; I feel my computer is more responsive with LnS than with Kerio 2.1.5..

 

An info from the avast! forum: http://forum.avast.com/index.php?topic=16136.msg137996#msg137996

Someone knows something about this update?

 

Now that is what I call a prompt response and that too for a freeware, I am going to ask Tom for the fixes done and post it here.

 

Thanks, Arup

 

Hi Arup,

I've just tried Tooleaky once again a few minutes ago.

Winsonar immediately blocked it, so i then allowed it to run.

I got an alert from ZA Free asking for Internet access which i refused ! A few seconds later i got the info box from Tooleaky saying there was NO leak.


StevieO

 

StevieO,

Run AH, and you will see it blocks everything and combined with ZA free or Filseclab, it offfers a good and free solution.

Vampiric_Crow,

You are most welcome, actually have installed Filseclab with the update on a ICS machine and LAN, so far runs very well.

 

This has not addressed the issue with Proxomitron. Anything can use it to connect even if they have been blocked. Maybe this applies to other local proxies. Again I have uninstalled Filseclab.

 

David,

Did you try making a rule for Proximotron to block inbound?

 

I decided to install the Filseclab on my clean Notebook, and works very well...

It passes the website tests, and I don't know if the new update have fixed something about the resources, but seems a little better now... Although, the resources usage should be improved at same...

I will make a feature request list to send to the developer...

 

VC,

Add AH and you will have the best combo.

 

I will try it on the next incoming version