I’m using Avast 8 and Comodo 5 under Windows 7, I put a block on IE9 with Comodo (I stick to Chrome these days)
Oddly I found that Google works and brings up results, however attempting to follow any of the Links is blocked by Comodo.
Unless as I had Chrome open The Google search was able to get out via this??
Since when and who fixed this issue? Did Avast fix this issue already? It did not only affect Comodo Firewall but also Windows one as well.
Egemen the head developer of CIS:
"The issue is avast intercepts WEB connections at the driver level and redirects connections to its own local proxy.
Because CIS operates at NDIS layer i.e. the lowest layer of the protection, it sees the actual connection i.e. avast proxy. Normally CIS should have blocked the loppback area connection to the proxy however because of the limitations in Windows 7, it fails.
CIS uses TDI, WFP and NDIS to provide its firewall functionality. WFP maybe enough ti implement an average firewall but it is not enough for a firewall like CFW so that it could not be used alone wihtout the support of the other 2 technologies. Windows 8 allowed us to use WFP more than previous windows editions and it should not be a problem with the next CIS editions which support Windows 8."
So Windows 8 is the only OS which don’t seem to have this issue. Windows 7 is still not fixed.
Asyn: Not sure if you were referring to my Post, but Comodo 6 seems to have a number of issues with CIS forum members, mostly related to Dumming down of the interface.
My copy of V5 is not picking up on any updates, so I have decided to stick with it for the time being.
V6 is dues an update any day now (should have been at the end of the month but it is late ??) I also want to see what effect this has?
But I guess I will update soon.
I use the latest beta build of Avast Pro Antivirus and the latest stable build of Comodo Firewall with Defense+. I haven’t done any exclusions. But both programs are now running fine without any issues like before.
that Comodo Firewall V6 (as V5 did) can not manage (allow block ask) any traffic that runs through Avast’s Network shield right?
I noticed I can block all this with Comodo Firewall if I apply a global rule that blocks any 127.0.0.1 (may be port: 12080 is needed) traffic.
Worse, I noticed the same accounts for little software called Proxifier! This is a legal nice and cool software I bought but! I can not controll its traffic, too, for the same reasons. SO ANY PROGRAMMER can write some piece of shitty code that uses this local proxy tunnel function and bypasses COMODO Firewall!
Avast’s netshield is there no help since it can never be as good as an experienced user that controlls in/outbound traffic via firewall manually.
I remember when this issue was first brought to the surface and users could not block firefox from connecting.
Well i have tested this theory myself and i can confirm that comodo does block outbound connections when avast is run in tandem.
Anyway the subject is moot because avast has a primary function of preventing malware from being installed so illegitimate connections should not be an issue and if any user feels there is a need to block any connections then those programs really should not be installed on the computer.
Comodo Firewall v6.2.282872 has avast on its “in program” whitelist. CFW v6.2 and avast plays well together.
I have never experienced any issues. It’s the CFW “behavior blocker” which creates the issue.
If you disable the CFW behavior blocker you will be fine.
CFW GUI>Tasks>Advanced Tasks>Defense+>HIPS>HIPS Settings>Behavior Blocker>untick the box and disable the Behavior Blocker.
i am using comodo internet security premium version 6.2. but i want to give a try avast 8 latest version with my comodo firewall version 6.2. can i use that .
is there any settings i need to change for this? 8)
but I have Comodo 6.2 and Avast beta and malicious test code can go out through Avast netshield virtual network adapter / local tunner proxy what ever technique and Comodo want pop in despite tight settings in Comodo: