[Direction]Source/Destination,In/Out and Local/remote,Both

Comodo Internet Security - CIS Resolved/Outdated Issues - CIS
1

example

CIS/CFP Style (Source/Destination,In/Out)
(In) Source:any (Local) Destination:server IP (remote) —X
(Out) Source:any (Local) Destination:server IP (remote) —O

(In) Source:any (Local) Destination:any (remote) —O
(Out) Source:any (Local) Destination:any (remote) —O

XXXX Firewall Style (Local/remote,Both)
(In) Local:any (Local) Remote:server IP (remote) —O
(Out) Local:any (Local) Remote:server IP (remote) —O

(In) Local:any (Local) Remote:any (remote) —O
(Out) Local:any (Local) Remote:any (remote) —O

Same problem, but CIS/CFP need two step/rule

Incoming rule
Source:server IP (remote) Destination:any (Local)
Outgoing rule
Source:any (Local) Destination:server IP (remote)

CIS/CFP In/Out Style only support “any IP<->any IP” rule.

2

??? ??? ???

Try again, please…

3

word “Source” mean, word “Destination” mean…

Source/Destination,In/Out = two rule (in and out rule)
(In rule) Source:any (Local) Destination:server IP (remote) <-correct???
(Out rule) Source:any (Local) Destination:server IP (remote)

XXXX = SKPF/SPF (KPF)

[attachment deleted by admin]

4

I was long term user of Tiny->Kerio->Sunbelt PFW.
I agree the concept Local - Remote In/Out/Both is more logical consistent
than Source/Destination one.

The poster pointed out this issue:

If I have u [/u] Rule in CPFW/CIS :

What is Source and what is Destination ?

If any to any, does not matter.
If not, Houston has a problem.

Edit: I would suggest ranaming tabs in rule dialog

Source , Destionation TO Remote, Local for Incoming rules
Source , Destionation TO Local, Remote for Outgoing rules
Source , Destionation TO one of above, which is valid for Bidirectional rules

In fact, I do not use any In/Out BUT any to any, otherwise I would report it before myself.