Bit Tornado

[Guest]

[JolietJake]

Thats cool.

Thanks Melih.


JJ

[JolietJake]

Bit Tornado now works and I am seen as connectable.
Great work people...

JJ

[panic]

Bit Tornado now works and I am seen as connectable.
Great work people...

JJ

Patience Jake. They might not get things fixed in the blink of an eye, but Comodo really respond to what users want.

ewen :-)

[mike6688]

Patience Jake. They might not get things fixed in the blink of an eye, but Comodo really respond to what users want.

ewen :-)

Patience is a virtue.  Especially with software development and Comodo are certainly quick with responses to any problems - so requires little patience.
 (L)

[ilkerka]

i fixed my nat problem in azureus using that rule aswell thnx. but the rule that we made isn't application specific so when azureus is closed wouldn't that port be accessible from internet?

[egemen]

i fixed my nat problem in azureus using that rule aswell thnx. but the rule that we made isn't application specific so when azureus is closed wouldn't that port be accessible from internet?

Nope. In this case CPF will adaptively block connections to that port.

Egemen

[greenhatch]

Hi. I'm new to Comodo firewall and use Bit Tornado. I don't quite follow all the advice given: I'm hoping the Noob video that is promised later would help, but in the meantime, could someone please help me thus (I'm sorry if it sounds silly, but I'm not very computer literate):
Which port number should I use for Bit Tornado, or is there a range I should use?
How would I move a newly added Network rule for BT above the Block IP In?
Thanks

[Damitha]

Normally The Client assigns itself a port number. Use that. And make sure it's in the not a well known port (less than 1024) And also if you are using two clients both cannot be the same. Best option is to use the one that's given by default.

When you add a rule to the Network Rules you can move it up and down.The option is available above the network rules table.Make sure all the blocking rules are at the bottom and the Allowed ones are at the top.

Hope this helps!

Regards
Dam

[greenhatch]

Thanks for the advice, Dam. I could not find where Bit Tornado assigns a port number; however I selected one at random (44444), added the rule in Network Rules and hey presto: the green light appeared on the next test torrent.   By the way, was it okay just to pick one port: I noticed I could have selected a range?

[Damitha]

ya it's better to stick to one than randomize.

next time select a port with different numbers like 45268 he he...

[greenhatch]

Okay Dam, I'll choose a new port number from now onwards. Presumably when the port  is not in use by Bit Tornado, Comodo can protect it, so that it's not attacked (fingers crossed!).

[Little Mac]

greenhatch, you may notice that after you close the p2p client, you will have a lot of logged events in CFP, blocking various incoming traffic, ICMP Port Unreachables and things of that nature.  The deal is that the torrent doesn't know you're gone yet, so there's still a lot of connections going on tha tare now being blocked.

With CFP, the network monitor sets the stage for allowed traffic; the application monitor works within that for allowed applications to do the allowed traffic.  By creating the network rule port-specific, there MUST be an allowed application up and running, to accept the incoming traffic.  If no application is active on that port, the network monitor will refuse the connection.  You are thus secure.  This is part of why you want to assign an uncommon port, fairly high in the range, so that it's not likely to be in use by some other application.

Hope that helps,

LM

[greenhatch]

Thanks for the further info, Little Mac.

[CNHS Coach]

the first rule worked like a charm for me...secret is restarting your bittorrent client!

[Smoky]

Bit Torrent does not use UDP so why not just a TCP rule?

[Tags:]