When I was prompted for an incoming connection to svchost.exe on port 135, I denied, then opened up the rule. The ip address was set to 0.0.0.0, so I’m guessing that is my computer. I’m also guessing that setting to “any” would refer to all remote addresses.
What I meant was: for example in network mon. rules, if I have direction=out, then the remote is the “outside” computer. If I have direction=in, then remote is my computer. ( In Sygate, this was called like the “point of view logic”). This is, as I found it explained by egeman in this forum.
So, if I take direction= in/out (both), what logic applys ??
The same could be in question for application rules.
I hope I made clear what I meant now.
Ok, I installed the new beta. Now it seems its all new logic in the popups.
Now, Internet Explorer isn’t needing “act as server”, I am even not prompted for that. I think, this is because the old version had some flaws in decide what is real inbound or outbound.
Eveb if I turn off “skip loopback” for TCP and UDP, I dont get a message that IE is trying to “act as server”.
THis issue wth Remote IP and Source needs to be sorted out once and for-all. I also would really like an “Allow Loopback” button for each application in the application control, so you can allow loopback for each process.
“Remote” changes depending on whther the connection is inbound or outbound. Currently this is confusing and could lead to issues.
Changing Remote to Destination would help remove the confusion BUT does not really resolve the issue.
Most other applications use Remote/Local and so would it easier to understand if you have used a firewall before.
More importantly, by having the IP fields switch dependent on direction means you cannot have a rule for combined in/out as the IP’s you have entered will be the wrong way round for one diection, yet this is an option in the dialogue when setting up the rule.