I seem to have an issue where the Firewall events are missing.
In the Summary screen it shows how many intrusions are blocked so far and then there are blocked intrusions, but when I want to look at them the Firewall event viewer is blank ? as if there were no entries ?
This is a fresh installation on a new laptop.
Windows 7 SP1 Home premium
I am not sure what is happening it would take a hugh amount of logging to have the need to delete when limit is reached with those settings.
Even if this limit was reached, I would expect it to only get deleted when more logs were created therefore I would expect some to be showing at all times ???.
If in doubt set it to save full logs to a specific location and see what happens, you can always delete these after if no longer required.
Sorry I am not much help here, if anyone else has some suggestions please do so.
I cannot upgrade to Sp3 as windows 7 x64 Home premium only goes up to SP1.
Sorry about that. Thought you were on WIN XP.
My setup is almost identical to yours. WIN 7 SP1 x64, Avast 6.x. I had no issues with Avast 6.x and Comodo 5.x other than with some Web Shield issues that are not related to your problem.
I did add Comodo’s cmdagent.exe and cfp.exe as Trusted Files in Avast’s Behavior Shield settings.
Radaghast will correct me if I am wrong on this but I am not sure intrusions are logged unless the rule that blocks them has “Log as a firewall event if this rule is fired” checked?
Do you have block global or application firewall rules where the above option is unchecked? If so Comodo’s firewall status screen will show the total number of blocked intrusions but no event will be placed in the firewall log.
I run Avast 6.x. The only thing I see in my firewall log is Avastsvc.exe which is used for Avast’s web shield and because I chose to log all events it generates.
BTW - Avast’s web shiield uses a localhost proxy that connects to port 12080 from your browser. It then connects to the Internet from localhost ports in the 12000 - 12999 range to the orignal destination port which is usually port 80. It only does that for http traffic. It does not do that for https, tcp, or anything else your browser might be connecting to.