Network monitor rules

Stupid question maybe, but what’s the point of setting up a source IP for outgoing connections? The source IP would always be my own IP right?

or another thing, some online photoalbums don’t work properly unless you add their address to your firewall allow list.
Most firewalls are less specific and only let you add an address as either allow or deny.
So how should I add the address to Comodo? (in or outgoing connection? source or destination connection?)
Can anyone explain?

Hi and welcome to the forum.

Source depends on the direction of the connection: if it’s outgoing then it’s your IP, if it’s incoming then it’s the internet or whatever the other end’s IP is. (Now just switch it around as vice versa for Destination).

Please see ** FAQs/Threads - Read Me First **

Understanding and creating network control rules,1125.0.html

Explanation of Comodo’s layered rules,5372.0.html

Summary of Network rules,5340.0.html

…and that is (imho) one of the strangely confusing things in the Comodo Firewall user interface. Since the DIRECTION of the connection is already clearly identified and controlled as IN, OUT, or IN/OUT on the GENERAL tab of both the Network Control Rules and Application Control Rules settings screens, there would appear to be no purpose at all to using the ambiguous words SOURCE/DESTINATION on other tabs. Why not instead just use the unambiguous words LOCAL/REMOTE, for both IPs and Ports?


Someone already put that in the wishlist:,6883.0.html

I started out with Kerio’s Local and Remote, so I was confused like you when I first switched to CFP. I just don’t like the idea to switch it back after being so used the terminology. Oh well. Different preferences will always exist, but there can only be one.

More important, what is source and what is destination, when we have an IN/OUT rule?
Man, is it in the manual? I guess i have to read it again, and stop testing other firewalls. I’ll go nuts!

No kidding. That’s why the idea of switching it local and remote isn’t appealing to me after becoming accustomed to source and destination. I found the manual at this holy place:
** FAQs/Threads - Read Me First **:

User manual,2958.0.html

You create rules sepparatly, unless it’s any- any.
Care to clarify why local and remote isn’t simpler- more functional ???

I don’t know if it’s a matter of which is simpler. To me it’s matter of not wanting to switch after being accustomed to something. If Comodo ever decided to change the terms then the rule system itself has to change.

Having used both, you must admit that “local and remote” is alot easier (less confusing) way of getting the job done? What about In/Out? Which is source or destination? ???


Admittedly, it is easier. Who would’ve thought the terms were based on the direction of the connection (I had to figure it out myself and through reading the forums when I first started).

That’s why I use separate In and Out rules. No confusion, and they seem to work better.

And Soya’s right - if they were to change to Local and Remote, the code would need to be redone, as that changes the rules scheme entirely. With Source and Destination, it directly coincides with Direction of traffic. With Local and Remote, they no longer coincide. I don’t know, but that may be why Comodo did it the way they did.