Open TCP Ports

[comoradh]

Hi there,

I happened to be running a scan of my system with CurrPorts when Bitcomet was up and running and I noticed that there are lots of TCP ports assigned to Bitcomet other than the TCP/UDP port that is forwarded on my router. I attached a screenshot. Does anybody know why happens is or if there is any cause for alarm? Thanks for your time.

Kind Regards

Seán

[kluelos]

What you are seeing is normal network application behavior. There is nothing to be alarmed about.

When a network application sends out a TCP packet, included in that packet is the reply address and the port to reply to.

The port number varies. An application does not always hand out the same reply port, quite the contrary.

The port you configured your router for is BitComet's "listen" port for initial contacts from outside. that and your IP address get sent to the tracker, which in turn sends this info to all interested peers. They can initiate contact with you on that port, since your client is listening for and expecting initial contacts on that port.

Once that initial contact is made (with that outside application ( whose packet ALSO includes the port that IT is expecting the reply on), then traffic moves off of your designated listen port and over to a different port -- or ports. Each TCP packet includes the port that it came from and the port it expects the reply on.

This communication is stateless and nothing says it's going to be the same port each time on either side.

[greywizard]

Besides BitComet uses by default random ports for outbound connections.

[comoradh]

Thanks for the replies guys, much appreciated, you've set my mind at rest. Cheers!