HELP me configure my CFP3

[Guest]

[AnotherOne]

I was afraid that program rules would not work - just too ignorant of the details for CFP.  Let's hope that Comodo adds port triggering as I requested:
http://www.portforward.com/help/porttriggering.htm
That would allow the listen ports to be open when the software is running without the ports having to be open all the time.

[gandazilla]

Instead of manually copying me, you want me to upload my config for you so that I you can import them?  Trouble with that is that they also include all the other settings in CFP3 including Defense+ that might not be applicable to your pc setup.  What do you mean by "what's my TCP port?"?

no no no, i won't copy them all.(can it be done anyway ).

Gibran taught me these : (creating port set)

incoming TCP port ==> add yours, what's mine

[Soyabeaner]

If you don't know what your TCP port set is, how do you expect I would know

If you mean the Firewall > Common Tasks > My Port Sets, then I didn't touch it.  It left them all at the defaults.  It doesn't matter to me anyway since I don't use them.


===
Ah....I see now you mean the port to open / create an an allow rule?  Firstly, mine is TCP and UDP for it, and secondly, it's for uTorrent.  If you don't p2p then don't create such a rule.

[gandazilla]

If you don't know what your TCP port set is, how do you expect I would know

, i've look for it in wiki, there are lots of port for TCP.how do i know which one of it 

If you don't p2p then don't create such a rule.

never mind then 

i've done playing with CFP3 then, i think this global rules : block IP in any/any/any covers them all.
now what should i play

[AnotherOne]

Which TCP port you use depends on the application that you are using TCP for.  For HTTP (browser) download managers, you would use port 80 for incoming data and outgoing requests, while for FTP you would use port 20 for incoming data and port 21 for outgoing connection requests.  You would also have to include an outgoing DNS lookup (UDP out to/from Any;source port any;target port 53).  This would be written as a set of rules for a particular program with the usual Block rule at the end.  Other ports apply for email and other applications.

[Munemasa Katagiri]

I use Emule and Bittorrent, I didn't create any special rule and they're working well so far.

[girltech]

Hi Girltech - You only need the multicasting rules if you are using internet based media streaming services.  See http://en.wikipedia.org/wiki/IP_Multicast for a bit of background.  You may need it for a home-based multimedia center computer if you are using it in conjunction with your TV or stereo components (not those built into your computer).  I don't quite know if this is so - I don't think it applies unless you have multiple computers involved.  I installed it because I was getting a blocked request for a connection to 224.0.0.24, which should be harmless and I don't like crippling features that are not a security threat.

The LAN and the LAN and Outgoing rules are rules you would have to write yourself.  Basically, you can write the rules for LAN without the multicasting option like this:
Firewall>Advanced>Predefined Firewall Policies>Add>(Use a Custom Policy)>Add
Allow IP in/out from (192.168.0.0-192.168.0.255) to (192.168.0.0-192.168.0.255) where the protocol is Any
Block and Log (Check "Log" box) IP in/out from Any to Any protocol Any
The address range might be different for your network (the router counts as a LAN address, so you have a network).  To see the IP address of your computer, click Start>Run>(type Cmd to open a DOS window)>(type ipconfig and press Enter)
The LAN and Outgoing "Predefined Firewall Policy" is the same with the addition of:
Allow TCP or UDP out from IP Any to IP Any; Source Port Any; Destination Port Any
This rule must appear above the Block and Log rule.
Sorry, I don't really know if the rules will transfer to the v.3 final update.  I have gotten into the habit of uninstalling Beta releases before updating.  I believe that there is an option to export your settings  (under the miscellaneous section) but I have not tried it, so I don't know if you can import the rules sucessfully.

Ok I think I understand a little of this.  In the LAN settings, the IP address you gave go on the Source tab and the Destination tab?  Is the Block and Log a seperate rule to be made?  And the 3rd is the LAN and Outgoing rule.  Sorry I know I am really new at this.  Back when I got V.2 one of the guys posted a picture of their rules and I just copied those but v.3 is so different that I don't know if those rules will work.  Thanks for the help.

[AnotherOne]

Hi Girltech - I've made a screenshot of a couple of parts of the process ( I see that I have left the "Log" box checked for the first screen shot - uncheck that except for the Block rule):

[girltech]

I understand the first picture but not the second.  How did you get three different things on the LAN & Outgoing page?  Under my LAN policy which is like the first pic all it says is Allow and log IP IN/OUT " ".  Could you attach a pic of your policy name page, too?  Thanks.

[gibran]

I understand the first picture but not the second.  How did you get three different things on the LAN & Outgoing page?  Under my LAN policy which is like the first pic all it says is Allow and log IP IN/OUT " ".  Could you attach a pic of your policy name page, too?  Thanks.

You need to create a new group in Firewall\advanced\predefined firewall policies (click add)
then you'll see a blank dialog where you can fill in a name for the policy (eg Lan and Outgoing)  and add your rules in order to make it like



Then you can associate this new policy to all application you want (in Firewall\advanced\network security policy applications.

[gibran]

BTW I've not tested this but Allow IP in/out from (192.168.0.0-192.168.0.255) to (192.168.0.0-192.168.0.255) where the protocol is Any
could cut out some legit lan traffic.


I guess it is better to create a Lan Zone with multicast and broadcast IP too

[AnotherOne]

The first screenshot is the first "Add" to the second screenshot.  To create the second rule, click "Add" again and write the second part.  Do that again to add the Block rule and your policy is done.  To create the LAN policy, "Add" a new policy, and then Add the same rule for the LAN zone and just omit the "Allow TCP/UDP out" rule and finish with the Block rule.

[AnotherOne]

If you need multicasting rules, see the following screenshot for the LAN policy.  It uses port sets defined on the "Common Tasks" page of Firewall.  Gibran has pointed out that there are LAN braodcasts to 0.0.0.0 and 255.255.255.255 as well as the port ranges listed above.  This seems to happen on my system already, possibly because of a Global rule for TCP/UDP out via privileged ports:
Allow and log TCP/UDP out where source IP is any, destination IP any; source port is in Privileged ports (Already provided in the setup); destination port is any
It may be wise to include the two IP extremes above in your LAN rules.

[bamaman66]

I have just downloaded the newest version of comodo firewall with the basic firewall.  Could someone point me to some instructions for setting it up or is it good to use in the default position?  It is very different than V2. 

[gandazilla]

I have just downloaded the newest version of comodo firewall with the basic firewall.  Could someone point me to some instructions for setting it up or is it good to use in the default position?  It is very different than V2. 

i've passed the "confusion phase" of configuring CFP3  .
if you don't need any specific rule (in other word: you just want to monitor what goes in and what goes out) : create this rule on firewall/advanced/network security policy/GLOBAL RULES :
block & log IP in from IP any from IP any where protocol is any
 

[Tags:]