Local-Remote instead of Source-Destination concept

It would avoid confusion in bidirectional connection policy
( both system are in fact both source and both destination )

Remote local systems positions would be more invariant both

in connection policy config windows - e.g. Local on left, Remote on Right
and in active connection list remote and local servers would be in their the only columns

+1 +1 +1 +1 +1 +1 +1

This is absolutely my number one wish for Comodo firewall! Get rid of Source/Destination and replace with Local/Remote, like most other firewalls!

We know that an outbound connection has as its source the local machine, and its destination the remote connection; and that an inbound connection is exactly the reverse, with the source being the remote connection and the destination being the local machine. But why, why, why make the user have to wrap his mind around this concept each and every time he wishes to make/edit a rule?!

Every connection involves the local machine (on which the firewall is running) and the remote machine. There is nothing ambiguous about this concept. No matter in which direction the connection, the local machine is always the local end, and the remote machine is always the remote end. Plain. Simple. Doesn’t require puzzling out source/destination terminology.

What’s more, with the current source/destination paradigm, a bidirectional rule (In + Out) is for the most part meaningless. The only time it actually works as intended, is when the source (address and port) and the destination are identical, such as when source and destination are both Any. Source/destination can be a single address (only use for this I can think of is Localhost), or can be a zone such as [LAN]. But if source and destination differ at all, then the same rule is actually two completely different rules: one for inbound connections and one for outbound connections!

With the local/remote paradigm, local is always local; remote always remote, and a bidirectional rule works as intended. It makes no difference whether the connection is inbound or outbound, the rule works the same way, and this is as it should be!

I understand that a strongly worded post such as this may tend to stir the ire of long-time Comodo users (and developers). Believe me, that is not my intent. I only wish to improve the user experience, and I strongly feel (How can you tell :wink: ?) that this would be one of the most important steps in that direction.