But maybe Comodo Group doesn´t want to post an official uninstallation tool because destructive people could use it to kill the Comodo Firewall Final Version.
I,ve tried setting up a zone. I´ve added rule a global IN Rule allowing all ip protocols IN. I have set up port sets. I have set up IP ranges I have tried doing it up with specific IPs and the broadcast IP(this is how I have it done in 2.4 with an ip rang for printers and servers)and I have tried adding ports 1 at at time I have set up a Both application rules in network security and global rules. I have set it up under aplication rules
I have gotten it to work after first reboot after install with a automatically it created a rule in Application rules
Application Name
-System
ALLOW IP IN FROM IP ANY TO IP ANY WHERE PROTOCOL IS ANY
ALLOW IP OUT FROM IP ANY TO IP ANY WHERE PROTOCOL IS ANY
The GLOBAL rules are the standard
Allow All Outgoing Requests
Block(and log) All Incoming Request It worked after the install reboot when I rebooted a 2nd time. It will quit working. I have reproduced this problem repeatedly.
Just a note: I do not like any Allow all IN rules on my system unless someone can explain why a rule like this is safe I will stick to 2.4. We’ll see what happens with the next release be it Alpha or Beta
My logs says
System, Blocked, UDP, remote IP Address, 137, Local IP Address, 137
System Idle Process, Blocked, UDP, remote IP Address, 137, Network Broadcast Address, 137
I have tried to create rules to allow this but CFP Alpha 1.0.0.0 seems to ignore these rules
also The allow all IP IN rule above should allow the above blocked traffic
I am currently having to use 2.4 and reinstall the apha when I have time to test
However I think When Comodo gets all the bugs out CFP v3 will be the best personall fire wall on the market and with a good management console it could be a great network IPS(R)
I installed the alpha after uninstalling 2.3 (2.4 blue-screens randomly). All available functions seemed to work fine, with the exception of the bugs and problems already reported by others. I however had the additional problem that (after adding the local subnet as trusted in the global FW rules) I could not see the other machines of the subnet in my Network Neighborhood folder. I could connect to these machines via Run: \server\subdir, so Comodo did not block stuff indiscriminately, however listing the available machines of the subnet did not work. Setting the FW to allow all did not mitigate the problem. Uninstalling the alpha and reinstalling 2.3 however did. Hope this helps. This product needs a lot more work before moving into beta…
All the best,
I changed the general settings of defense+ at “allow all”; i clicked at “apply”. After that i rebooted my system. I was surprised; also the firewall security level was changed to “allow all” automatically (!!!).
That must be a great bug, i think.
The one function is the “internet firewall” and the other function is the “system firewall”.
Firstly, I find the presence of the Exclude option in the Add screen… a little odd… especially since you’re adding IPs, ranges, etc… to be blocked. Double negative logic. So, an Excluded My Blocked Network Zone is… not blocked? I guess that you might have a blocked range & have a need to exclude 1 or 2 of the IPs in the range.
Secondly, there seems to be a bug in this section. If I create a block for any IP, IP range, hostname, etc… (haven’t tried the MAC addresses yet) I loose my entire Internet connection as soon as I hit apply. It doesn’t seem to matter if I use the Exclude option or not (of course! 88))… or if the IP or hostname actually exist at all. As soon as I remove & apply whatever it was I created, then my Internet connection is restored. So… this is really the disable my network function?
THis was a allow all TCP or UDP out in v2.4
The Allow IP OUT is based on the premise that if your computer requests a connection and the Application requesting the connection is approved by you then the reply to this request also need to be aproved in order for ther applicatio to complete the requsted task. Prefered to limit my ports out to a few selected ports and had it working very well in 2.4 even on my untrusted lan I only allow incoming connection from a few addresses. And I delete rul 1.4 that allows GRE out as I don´t us VPN
It looks like CPF Alpha has remove the Block all rule and made this implicit in the Alpha
The default rules from My CFP 2.4 Install
1.0. ALLOW TCP or UDP OUT FROM IP [Any] TO IP [Any] WHERE SOURCE PORT IS [Any] AND DESTINATION PORT IS [Any]
1.1. ALLOW ICMP OUT FROM IP [Any] TO IP [Any] WHERE ICMP MESSAGE IS ECHO REQUEST
1.2. ALLOW ICMP IN FROM IP [Any] TO IP [Any] WHERE ICMP MESSAGE IS FRAGMENTATION NEEDED
1.3. ALLOW ICMP IN FROM IP [Any] TO IP [Any] WHERE ICMP MESSAGE IS TIME EXCEEDED
1.4. ALLOW IP OUT FROM IP [Any] TO IP [Any] WHERE IPPROTO GRE
1.5. BLOCK and LOG IP IN or OUT FROM IP [ANY] TO IP [ANY] WHERE IP PROTO IS [ANY]
I love version 2.4 :BNC, but the alpha version seems to error out after a short while. (:AGY) It seems to happen when I double click on the icon and I have Windows Outlook 2000 open. I noticed the same problem using the Microsoft Web access for Outlook 2003. The firewall pops up with a warning that it encountered a problem. The next time it happens, I’ll send the dump to the email provided. Once they get this thing working it looks like it will replace SSM.
scanning the ports of the machine doesn’t give a warning that the pc is scanned.
i couldn’t find any log where a portscan is sighted and blocked.
(portscan didn’t get through)
Can somebody prove please:
No firewall popup if anybody wants to access the pc with the firewall running.
Al, you may have to find the dump, zip it, and attach to your post under Additional Options. When I tried to email it, it kept getting returned for some reason. But maybe that was just my server…
Anyway, if you have to find the file to attach, it’s in Program Files/Comodo/Firewall. I forget the name now, but I think it’s ‘crash.dmp’.
Hello Comodo fans! Have been a user of FW 2.4 for about a year, no long lasting issues/virus/trojans etc. Decided to give the alpha firewall a go…I have installed, uninstalled & reinstalled about 4 times. Used the Uninstalled program it works like a charm. I have not had a BOD or a system crash—I just can’t get on line? I use firefox 2.003 & the latest version of Opera. Once I click to get on either one I get an error message that says the connection was reset…I’ve rebooted when that happens & try again with the same results…The firewall is set at the default config. I get a few fw/operating system warnings ie., how to accept/deny Wuaudt.exe or OOD2000.exe when I go into the firefox browser to go online. Anyone have any ideas/thoughts. WindowsXP with sp2 (32 bit)
This might occur if your IP is assigned by DHCP from a router or from your ISP. If from a router, set up a zone that encompasses all IPs on your LAN including your router (FIREWALL - COMMON TASKS) and then add a global policy using this zone (FIREWALL - ADVANCED - NETWORK SECURITY POLICY - GLOBAL).