Comodo Firewall

  • Thread starter Thread starter Deleted member 78630
  • Start date Start date
  • Tags Tags
    firewall
D

Deleted member 78630

Guest
For the past few months I've been using Eset for my security needs and it's time to move on.

So far I'm liking everything about Comodo, except I can't manage to set up the Firewall in the way that I had with Eset. I was able to add the rules that I thought would do the job, but to no avail.

All I needed to do with Eset was to apply 3 rules to an application.

* Allow everything
* Disallow all traffic to remote port 27030
* Allow traffic to remote port 27030 on IP 41.185.60.43

Essentially only allowing the IP address (41.185.60.43) on Port (27030) for the application.

In tabular form:

Code: 
                            Action  Direction   Local Port  Remote Host     Remote Port
Allow All                   Allow   Both        Any         Any             Any
Block Port 27030            Block   Both        Any         Any             27030
Allow THE IP on 27030       Allow   Both        Any         41.185.60.43    27030


Please assist and help me achieve the same with Comodo.
 
I don't know Comodo, but usually the sequence of those rules are very important. Have you tried swopping those last 2 rules? Maybe it stops at the 2nd rule [block all] and never get to the final rule? (Or are you still trying to find out how to set up rules in Comodo?)
 
Thanks for your reply and yes I do know how to configure the rules.

And your plan might just do the trick, I will post back shortly.

I don't believe it, your suggestion worked exactly as my rules for Eset had worked.

diabolus for president :D
 
Last edited by a moderator:
Good to hear. That looks like the WebAfrica Steam server, i guess you can always use Steamwatch for that too? [it basically do the same thing, but i think it's easier to turn it off though] .
 
Yes it happens to be the WA steam server. And I've used SteamWatch in the past and I can tell you that using a firewall is much better.

When using a firewall, the steam application is denied any access on port 27030 except for the WA steam server on port 27030, thus preventing the application from even starting a connection to any other server.
But when using SteamWatch, steam manages to establish a connection to other servers and thus leaking a bit of bandwidth before SteamWatch closes the connection.

So the only upside to using SW would be the fact that it is easier to close when needed to do so.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X