Tutorial for Utorrent with Comodo Firewall 3

[Guest]

[3xist]

I know. I didn't call him a n00b. I just gave him some advice. Still, it is frustrating when people post a question in a thread that was answered in the very first post in said thread. I just don't understand the thinking behind it.

It's also used for emphasis. There's a difference between making a whole post in caps and using caps to emphasize important words.

However, "emphasis" can be taken the wrong way, especially in that situation. Anyway, It can be frustrating, But just gotta maintain a bit of patience to new forum members & direct them accordingly

Thanks. 

[hullboy]

Rule 4
Action = Ask (enable Log as a firewall event if this rule is fired)
Protocol = TCP
Direction = Out
Description = Rule for HTTP requests
Source Address = Any
Destination Address = Any
Source port = A port range = (start port = 1025 / end port = 65535)
Destination port = 80

What's the "bug" you are talking about in the first post? (the one that suggests to set ALLOW instead of ASK in the 4th rule?)

[kail]

Hi

There was a bug in a previous version of CFP 3 that prevented the Ask rule from working. It is now fixed & this rule should work as advertised.. ie. it will Ask.

[Metalfyre]

Hi, I am using the latest version of Comodo Firewall Pro and after setting the rules like formentioned:

Rule 1
Action = Allow
Protocol = TCP or UDP
Direction = In
Description = Rule for incoming TCP and UDP connections
Source Address = Any
Destination Address = Any
Source port = A port range = (start port = 1025 / end port = 65535)
Destination port = the port of utorrent

Rule 2
Action = Allow
Protocol = TCP
Direction = Out
Description = Rule for outgoing TCP connections
Source Address = Any
Destination Address = Any
Source port = A port range = (start port = 1025 / end port = 65535)
Destination port = A port range = (start port = 1025 / end port = 65535)

Rule 3
Action = Allow
Protocol = UDP
Direction = Out
Description = Rule for outgoing UDP connections
Source Address = Any
Destination Address = Any
Source port = the port of utorrent
Destination port = A port range = (start port = 1025 / end port = 65535)

Rule 4
Action = Ask (enable Log as a firewall event if this rule is fired)
Protocol = TCP
Direction = Out
Description = Rule for HTTP requests
Source Address = Any
Destination Address = Any
Source port = A port range = (start port = 1025 / end port = 65535)
Destination port = 80

Rule 5
Action = Block (enable Log as a firewall event if this rule is fired)
Protocol = IP
Direction = In/OUT
Description = Block and Log All Unmatching Requests
Source Address = Any
Destination Address = Any
IP Details = Any

... I noticed I have problems with one certain tracker (which has it's anounce on port 81)

If you have connectivity problems:
Go at Firewall -> Common Tasks -> Stealth ports wizard and select
Alert me to incoming connections- stealth my ports on a per-case basis

Because of a bug you must change the rule 4 (for HTTP requests) to allow. I hope this will be resolved with the next updates.

Did that as well and....

If you have just a modem, you may need to add a rule (above the last block all) to allow outgoing DNS requests such as:

Action = Allow
Protocol = UDP
Direction = Out
Description = Allow Outgoing DNS
Source Address = Any
Destination Address = Any (or your ISP's DNS server for extra security)
Source port = Any
Destination port = 53

.. did that as well.

still it's being logged as the only tracker that's being blocked by CFP.

I even added an extra http rule where I allow outgoing http traffic to port 81 and called the rule: Rule for HTTP requests 2

So it seems all should be ok, yet still CFP blocks the event. Am I missing something here? Why is only that specific tracker being blocked?

I even disabled the firewall completely but then still it's being blocked. Now one might say that it's the tracker itself refusing it, but it's not. Cause if it were, then why do I get to see http traffic to that specific tracker on port 81 is being blocked in my firewall events?

I even altered rule 2 and 3 to where the destination port range is set from 80-65535. Still no go

[edit]Never mind, with the last mentioned sentence I did manage to make it work. Somehow the rule didnt change even after applying it, so I removed rule 2 and 3 and made them anew with the destination port range of 80-65535. Now it works. Love it when I can solve my own problems [/edit]

[Tags:]