Sorry for the late reply. I’m using a fixed IP address not the one provided by my ISP and it’s one that I created from my router. I reckon you are right Soyabeaner. I don’t think it has anything to do with Utorrent. I think the ISP provider at my parents had some sort of block before 12am as it took forever for the DHT to log in. However, now that I’m back at my own place with a different ISP the connection is always green.
I do have a question about my rules though, I didn’t create the top two rules for utorrent I think it was when I clicked allow utorrent to access the internet. I wonder if it’s safe to leave it as it is or should I block those two?
Actually I just tried blocking those two rules and utorrent won’t work if you do. But is it safe? I suppose it’s only accessing the port that I designated…
Instead of blocking them, just delete them.
uTorrent should work fine with TCP/UDP In [incoming connection port] and TCP/UDP Out only (and global rule).
I’m not using those two rules, and it works just fine for me.
Thanks for the great tut but I’m running into a little error. I’ve checked that I have all the info in correct but still uTorrent is staying red, but then I removed step 5 and it turns green. Do you have any idea what could be wrong.
Well i can’t seem to get pandlouk tut to work and would really like the more secure way, but got Ragwing’s tut to work so thanks
But if anyone wants to help me get pandlouk’s to work then go right ahead. I think with pandlouk I’m not sure what global to set with his because rule 1-5 I just have it just for a program and it doesn’t work.
I can understand how confusing it can be between App & Global rules. This was the case when I started with v2, and now it’s become more complex with v3. But after kicking around I’ve learned there is no “right” way of creating rules. Rather, there is “more than one” way of creating rules to achieve the same security level. That’s where v3’s flexibility comes in.
And I think I got it, i did what the first one said and added a global, out from my ip to any ip and dest port to utorrent port, and that kept my utorrent green
I’m not sure above the current version, but I find that the Alert me to incoming connections Stealth Ports Wizard option isn’t as secure as I like it to be. After monitoring my log for long while, I began to wonder why I no longer see Windows Operating System and System process with all the blocked ICMP traffic as I did in earlier versions. That’s because that SPW option doesn’t block WOS and System :o. This is where it might get more confusing because those 2 processes are, in a way from my perspective, a substitute for the Global Rules.
In essence, depending on which SPW option you selected, it can affect how you should handle creating rules for those 2 processes.
If you previously ran utorrent and set the “Treat this application” popup BEFORE discovering pandlouk’s setup procedure, you will get stuck on step 3 (like I did). If so, then do this:
Go to Firewall, click on Advanced, then click on Network Security Policy.
Find where utorrent is listed and double-click on it.
Under Network Access Rules, set the Predefined Policy to “utorrent”.
After downloading Comodo V 3.0.17.304 and restarting the system, the settings by pandlouk no longer seem to work. Even after using Racer_X’s advice on resetting it to the utorrent policy. Anyone else experiencing the same? Or is it just me?
Update: Hmm that is odd, I just started a torrent, and the icon is green, saying that the connection is as it should, but if I test the port at http://www.utorrent.com/testport.php?port= (port number) it says the port doesn’t appear to be open. Now I am confused
Update 19-02-2008:
Don’t know how or why, but it somehow works again. Meaning that both utorrent and the website shows the port as being open.
I’m eager to hear if pandlouk has any new advices or edits for this setup regarding the 3.0.17.304 version.
After upgrading to the latest version, CFP3 asks for TCP Port 80 permission to 77.247.176.151 (tracker I think). If I allow it, utorrent works fine, if denied, it won’t work at all.
All settings from the first page were left untouched trough the upgrade.
Looking at the CFP3 utorrent logs prior to upgrading to latest version, the same IP TCP and port was automatically blocked and logged…
One more thing, after the upgrade when it asked me to reconfigure or something to that nature, I chose to keep the existing configuration.
WomenAreMen, yes on this system as well, the icon is green yet the test shows port closed.
Hello ,I have the same problem (port 80) , and moreover since the update the icon of connections is in yellow, and when test the port it says that is close, but, so far , it seems work right.
Yes, I have double checked TCP Port 80 to 77.247.176.151.
Thanks for mentioning it, now that I looked in the Firewall Event log prior to 17.304 upgrade, the very same TCP port 80 and IP was automatically blocked and logged per pandlouk’ setup YET utorrent was functioning correctly.
Nothing was changed, at least manually, in the utorrent Policy.
Just a small question, after an update of COMODO, it told me that it was recommended to reconfigure the settings of the firewall, so the Predefined Policy were all erased. I ran Azureus and then the downloads and I dind’t have any problems, everything was running smoothly. But then again, should I re-create a Predefined Policy for Azureus or could I just leave it like that? I mean, will I get a better speed or something like that?
I combined P33gles Q and Ragwing’s A in order to describe the situation. Thanks.
Strange thing happened today with uTorrent 1.7.7
I never had any problems with the above since Comodo v2.xx
The rules as per “Ragwing”. Thanks to you and to all contributing to manuals.
The move to v3.0.17.304 brought some surprises but I reset rules the same way as it’s shown on the quoted image. The only difference was – Comodo did not create “In Protocol rule”. It was only Out ??? I did not pay attention to that and added needed two rules below.
Everything worked fine until I read this thread today and decided to remove the top rule.
After that all went bananas!
the first and every start Comodo fires this Orange Alert see below (which means ???);
I may or may not respond to it – the torrent will start both directions;
I may move the Global rule above or below Blocking one – it does not matter
uTtorrent may go green (port forwarded correctly, I did not change a thing) or it may stay RED … see the speed at the very beginning of this session;
I can close/restart uTorrent, move Global rule wherever I want… Green, Red Orange message unanswered - never mind - speed reaches 700-800 – Bob’s your uncle!
The other strange thing is – I usually have like dozens blocked IP using IPfilter… Now there are NONE! (IP-filter wasn’t changed).
Just to quickly point out that I followed pandlouk’s rules and they work for me, except that I needed to add an “Allow outgoing DNS requests” rule (like the one in the predefined web browser rules) in order to be able to connect to private trackers.
Same problem, but solved it without global rules:
Allow \ TCP or UDP \ out \ any \ any \ any \ any
Allow \ TCP or UDP \ in \ any \ any \ any \ [port]
Allow \ IP \ in/out \ any \ any \ any
I tried everything else on Comodo 3.0.18.309 and I mean EVERYTHING else for a whole day or so, nothing else would give me “green” and “correct port forwarding”!
That last rule you list, “Allow/IP/In-Out/Any/Any/Any” is not good to have running… It Allows ANY unsolicited Inbound traffic with ANY protocol access to ANY port on your machine. With that rule in place, of course your p2p works, and the two rules on top of it are meaningless. Heck, I can practically run p2p from my machine on yours with that setup.
All joking aside, that rule is a really big security risk.
One thing that’s frequently overlooked is that you have to disable UPnP settings in your p2p app, so it won’t randomly select a port. That way you control the port(s) being used for both TCP and UDP, and configure the FW to match.
