Nice, it worked, i haven’t played around with eMule yet but getting the last of Norton off my machine is a step in the right direction. Either way i should be fine now, i realized my IP isn’t static, so fixing that is another step in the right direction.
I just installed Comodo and it was notifying about all my apps, with exception of emule which it automatically allowed to connect outside but not be connected from others, and I was with lowid. I configured like this first tutorial and now I’m highid
I just recently switched from Norton firewall to Comodo and I have a problem in regards to Emule. I set the rules for incoming as defined in the very first post of this thread. I was wondering if I need to change the rules to in/out? How will I be able to upload if I don’t?
By default there is a Network Monitor rule to Allow TCP/UDP Out from Any Source to Any Destination on Any Port. This should cover your uploads. From that point you just need a rule (or rules) in Application Monitor to Allow emule the appropriate Inbound and Outbound communication. I would recommend them being separate rules, since you’re using specific ports for Inbound connection, so it will match up with the Network Rules.
I read your attached tutorial - “How to set up individual applicaton on specific port(s)”. I applied the tips to utorrent.exe under CPF Application Control. uTorrent is working just fine.
I also use eMule a lot. I wondered if I could apply the same logic to restrict ports used by eMule as well. I made such an attempt to restrict ports (TCP/UDP IN) with apparent success - both eD2k and KAD networks connect with HighID and eMule is downloading and uploading files. Guess I can’t restrict ports (TCP/UDP IN) for eMule for obvious reasons.
The below is my resulting Application Control rules for emule.exe with screenshot for Destination Port. Please kindly confirm my settings are secure and correct.
eMule.exe Application Rules:
Action: Allow
Protocol: TCP or UDP
Direction: In
Destination IP: Any
***Destination Port: A set of ports: 8111, 9222 (examples only)
Miscellaneous: None checked
I just came back home and fired up my eMule. Suddenly the eMule log window is showing port errors.
6/8/2007 12:32:05 AM: Failed to open port 8111 (TCP) on internal WinXP firewall for this eMule session
6/8/2007 12:32:05 AM: Failed to open port 9222 (UDP) on internal WinXP firewall for this eMule session
Weird…in spite of those errors, my NeoMule seems to be working just fine.
Tested ports using the official eMule test page…all TCP and UDP tests passed
Got HighID right way
Downloading and uploading just fine
I am unsure if the errors are really related to CPF. Since I started seeing after I installed CPF I posted here.
Should I be concerned? Beyond that is really going on? Btw Windows XP SP2 firewall of is disabled.
Followup:
Seems I found the clue…
With eMule added to Windows Firewall Allowed list, eMule will give the above port errors if Windows Firewall is disabled. Oh well…
I came to this link tnx to a caritative spirit on WildersSecurity other firewalls forum
Short story:
While looking for a super-light and fast network security application to control outbound connections I decided to install CFP to give it try. It may not be the lighter or most resource friendlier firewall but it’s an excelent alternative, better than more than one -expensive- commercial solutions out there while remaining free.
Everything was right until I started p2pering. The system nearly colapses when I launched eMule (eXtreme Mod 6), uTorrent, Opera browser with more than 30 tabs and Outlook 2007… nothing to say about Winamp that sounds horrible crippled. Please figure at that time my system was slower than an XT (yeah, with the 8088 cpu).
So, is there a way to tell CFP to don’t check at all some [trusted] applications? I mean not just allow all traffic because it indeed requires some type of processing but just to ‘watch to other side’ when [trusted] network intensive applications are launched.
[b]Version 2.4 - cpf.exe and High CPU[/b]
https://forums.comodo.com/index.php/topic,6819.0.html
https://forums.comodo.com/index.php/topic,6933.0.html
https://forums.comodo.com/index.php/topic,6943.0.html
Kalispera.Graftika simera.Kapou eida oti o filos Panagiotis(Global Moderator),egrapse Ellinika.Mporo na grafo kai ego se Greeklish, epeidi den ta kateho kala ta Agglika?Efxaristo poly.Giorgos
I use utorrent and I have a Netgear RP614V3 router with uPnP enabled and I have no problems at all.
Can someone explain the difference between port forwarding and UPnP? UpNp simply automatically forwards the ports when the app is launched and then closes them when the torrent client is shut down for security. That way you don’t have a permanent hole opened up in the router. Other than that, how would comodo tell the difference between port forwarding and Upnp? What causes the problem?
Ok, also someone mentioned that utorrent only needs TCP. when I leave UDP out of the firewall rule I get tons of blocked UDP packet to the utorrent destination port. Are you sure that utorrent doesn’t need UDP? My router’s upnp is forwarding BOTH TCP and UDP. There must be a reason.
Hi Rob, I’m using the same netgear router and also utorrent. Once I had set up the rules in Comodo I didn’t get the green triangle either. What I had to do was open a port in the router’s firewall. If you use this website
it should take you step by step through the process.