Which rule caused the block, killing all process's connections

Hi.

  1. Is there any way I can see which rule caused a logged block?
    Or is there any intention to implement such a mechanism in the next versions?
    It sometimes takes a lot of time to hunt down the exact rule that blocked a connection…

  2. Is it possible to kill all the connections of a process all at once?

  3. Is it possible to block a process temporarily from accessing the internet?

Thanks.

Hi Sosl,

There’s not buy it has been said before and it would be a neat feature, let’s hope. :slight_smile:

Anyway it shouldn’t take that long, just remember that for outbound connections the app rules are checked before the global ones, and for inbound the other way around.

2. Is it possible to kill all the connections of a process all at once?

Currently it’s possible to kill all the connections of all processes, but not of one process: “block all” mode or “stop all activities” in the summary page of the interface.

3. Is it possible to block a process temporarily from accessing the internet?

Other than manually editing the rules, and the answer to your previous question, currently it’s not.

You may want to post in the Comodo Firewall Wishlist for features you’d like added in future versions.