[HOWTO]Use CPF2 with P2P Soft(eMule,BitComet)

Help for v2
#1

eMule Network control rules

1 set eMule use TCP Port:4662,UDP Port:4672 in eMule
2 CPF–>Network Monitor Add 2 rules

[b]ALLOW TCP IN FROM IP [Any] TO IP [Any] WHERE SOURCE PORT IS [Any] AND DESTINATION PORT IS 4662

ALLOW UDP IN FROM IP [Any] TO IP [Any] WHERE SOURCE PORT IS [Any] AND DESTINATION PORT IS 4672[/b]

You can change Any to your static ip like 192.168.1.2

Bitcomet Network control rules

  1. Set your Bitcomet or other BT client 's listening port. example : 54321

  2. CPF–>Network Monitor Add 1 rules

ALLOW TCP/UDP IN FROM IP [Any] TO IP [Any] WHERE SOURCE PORT IS [Any] AND DESTINATION PORT IS 54321

You can change Any to your static ip like 192.168.1.2

Remember to add these rules before the blocking rule(BLOCK IP IN FROM IP ANY TO IP ANY WHERE IPPROTO IS ANY). Because the network rules are searched from top to bottom.

Hopefully to help someone else in the future. :slight_smile:

Open ports to allow P2P clients: The risks [RESOLVED]
#2

Great!.. Keep up the Good Work!

Cheers!

#3

Hey guys,

Thanks for the tutorial… Works great and getting really fast transfers on Azureus (:KWL)

I just have one concern tho… I probed the port I am using for Azureus and it is wiiiiide open according to GRC (www.grc.com)… I am using a port in the range recommended by Azureus.

Does this wide open port pose a risk? Is there not a way for the network rules to apply only to Azureus?

Would be nice if the author of the stickied post (or someone else who knows) could clariy these risks to noobs like me :wink:

Thanks for your help!

(J)

#4

That’s exactly what I did with mIRC so I could use DCC and I had the exact same question and problem but no answer.

The port is wide open, right? For all TCP/UDP incoming through port ####, it isn’t only set to be allowed by mIRC.

I’d like to be enlightened. :slight_smile:

#5

This question was answered by egemen:

" When you open the port, if an application listens on that port, it will be shown open. But if you close the listening application, it will be stealhted.

So the fact is “If Azerus is running and listening on the port you allowed in network rules, that port will be open. If Azerus is not listening, it wont be.” "

https://forums.comodo.com/index.php/topic,1556.0.html

#6

Obviously, I already know since I’m the 2nd guy that asked the same question in that thread and am VERY SATISFIED with the answer. :slight_smile:

#7

i just switched from zonelab firewall to comodo like 10 minutes ago, i read about your port settings and made the adjustments how ever i am still getting extremely slow download speeds, and that is if they are downloading at all, with azureus and zonelabs has never given me any problem like that. (i switched because zonelabs has a stupid bug that you can’t uninstall it from windows add remove programs, i did before i knew about the error and now i can’t reinstall zonelab, but good riddance i like comodo better.)

(B) (L) (M) (R) (S) (V) (:CLP) (:NRD) :slight_smile:

#8

Dumbass noob question…can I use Bit Comet with the Comodo default settings? What difference does it make if I tweak as shown above compared to the default?

It seems to be working ok using the defaults but not sure if I would get any more out of it by changing the settings.

Cheers guys.

#9

with default settings, CFP will block all remote access to your pc, include the port you have set in BitComet. That means the download rate may slow down because BitComet can not connect from Remote Iniatiation Peers .
if you tweak the settings like me, the download rate may boost up because it can now connect to more peers than default settings.

#10

Hi!

I’ve been using comodo for some time now and it’s a great firewall. But I can’t get utorrent to work properly.

I’ve done the settings ubuntu descibes, but it doesn’t work.

The problem is, to get “port open” in utorrents port checker I have to turn off comodo (allow all), start utorrent then switch on comodo. I can’t just start utorrent because then it shows “red lights” in the port checker (and slow downloads).

Does anyon know what the problem is?

Best regards.

Robe.

#11

  1. run utorrent , in Options → Preference → Connections
    untick “Random port each time utorrent starts”
    untick “Enable UPnP port mapping”

  2. Add Network rule for utorrent (the port must equal to Listening port in utorrent)

  3. run utorrent , in Options → Speed Guide
    Click “Test if port is forwarded properly”

if you got like this, the port is properly forwarded.

Checking port xxxxx on xxx.xxx.xxx.xxx...

OK! Port xxxxx is open and accepting connections.

You will be able to receive incoming BitTorrent connections.

#12
  1. Didn’t have UPnP unticked. Done it now but still don’t work.
  2. Done. Rule nr. 0.
  3. Done. Not forward correct.

Do you have other tips?

Thanks!