Well, indeed I have to admit there are some changes in Web Shield behavior as I have a minor problem with it (not this one), but it does not happen with my Vista machine, only with Win7 machine.
What are your OSes, all have Win7? And all have Comodo in your computer?
From what I’ve seen and read, the problem is specific to Windows 7/Avast 7 (web-Shield)/Comodo and Windows 7 firewall. Does anyone know if Comodo use Windows 7 Base Filtering Engine?
Have they worked out if this is Windows 7 32-bit or 64-bit or both yet?
Pretty sure Comodo doesn’t use the W7 Base Filtering Engine since I imagine it wouldn’t be so good if it did, its not like Windows 7 Firewall Control which apparently also has this bug conflict with the new Avast! 7 Web Shield and besides Comodo FW installs the entire bulk of CIS so why would it as an overly full third party FW?
I was just curious about the reasons why, both CIS and the built in Windows 7 firewall, have the same problem. It seems logical to conclude there’s some shared functionality. As a number of third-party firewalls use the base Microsoft code, this was a natural assumption. As far platform, it affects both 32 bit and 64 bit versions.
no solution yet?
Hi Hardov,
No Solution yet… Not even a response from a Avast team member.
Two work-arounds:
Disable Webshield. - Comodo will work perfectly, but no web traffic will be scanned.
Enable “Scan traffic from well-known browser processes only” - This will allow Most connections to be blocked by Comodo, but popular software like Mozilla and Thunderbird will go through unhindered.
Ok thanks so muchs for the help!
Hi All,
Updated to the latest version today.
Cleared my rules and tried again.
Firefox still connects like there isn’t a care in the world even though it is explicitly blocked and Comodo logs it as blocked.
Hi guys,
this is really very interesting. Matousec’s leak tests show 100% for COMODO, yet, apparently the firewall is not able to catch a Web proxy which our WebShield is.
I am not saying that Comodo is a bad firewall, on contrary, it is highly regarded, but maybe this might be a contribution to the relevancy of the leak tests – as I see it from my brief glimpse on this issue, any program acting in the same way as avast does can overcome the firewall rules. Somewhat surprising for a product with such high leak-test “certification”.
Concerning the fix from avast! side: I doubt we would fix this, making changes in the code, so that other firewalls block our traffic is exactly the opposite what we try to do.
Nice comment on the Comodo forum from the moderator though:
Re: Comodo Does not work with Avast 7! « Reply #3 on: February 24, 2012, 06:27:55 AM » This seems like an issue with Avast. They changed the code. They will have to fix it.
I only hope that malware and unwanted programs follow the same guideline.
Lukas.
Well,no problems here…my firewall is on medium…and i have turned on block fragmented IP [since i dont use printers]… 
Hi Lukor,
Thanks for your comment on this!
Regarding Matousec… I do not trust in the legitimacy of those tests anymore.
According to them Comodo is the only FW that works and everything else is crap… Different firewalls work in different ways and I believe their testing to favour certain Firewalls more than others…
But Comodo is a good and very popular FW.
That being said, I believe there to be a very large number of users affected by this and it’s a serious issue.
I bug report has been submitted to Comodo, but there has been no sign of a fix anywhere.
Hi Hellion,
we have changed one driver in the v7. We abandoned the old and not supported TDI interface and started to use the new one (well, its already a few years old, but still newer) - WFP. I bet this is why Comodo has now troubles filtering our proxy requests and while at the same time allows traffic from the avastsvc.exe (where WebShield is hosted) these things together create that hole.
I would love to help Comodo understand the method we currently use and help them change the firewall in such a way that they are able to see and block that - should I be contacted by anyone.
The method we use is fully supported and documented and from several meetings with other companies I know for sure there are several (if not many) major products out there that use the same - so I guess such fix in Comodo will help not only Avast users but also many others.
L.
Hi Lukor,
Thanks, that was very clarifying.
Here is the Comodo forum discussion - https://forums.comodo.com/firewall-help-cis/comodo-firewall-and-avast-7-t82382.60.html
Here is the Comodo Bug report - https://forums.comodo.com/bug-reports-cis/cis-firewall-fails-to-block-connections-for-blocked-applications-with-avast-7-t82440.0.html
Hi All,
Well,no problems here...my firewall is on medium....and i have turned on block fragmented IP [since i dont use printers]... :)
@ Winmaltech,
You do know that streaming video also uses Fragmented IP packets
LOL ;D
Thanks for posting lukor. I’m not sure if you noticed my earlier post, but this is not confined to Comodo, it also affects Windows 7 built in firewall, which obviously uses the Windows Filtering Platform. So, the question is, as I asked earlier, does Comodo use WFP and, if so, does this mean that any firewall, also using WFP, can be bypassed by this change?
By the way, the Matousec tests are HIPs tests, not firewall tests, which is why they’re completely irrelevant.
PrivateFirewall is also affected.
No issues with online armor…
yeah I already had a good laugh about that ROFL ;D
What about Online Armor Free? can we use Online Armor free?