Hi, could anyone explain to me these weird connections created by Ktorrent?
Should I be worried about my privacy?

Code: Select all

maf@firebird ~ $ netstat -n|grep ":... "
tcp        0      1 10.0.0.2:39633          87.16.49.46:161         SYN_SENT
tcp        0      0 10.0.0.2:32833          80.53.72.62:80          TIME_WAIT
tcp        0      0 10.0.0.2:32830          80.53.72.62:80          TIME_WAIT
tcp        0      0 10.0.0.2:60903          80.53.72.62:80          ESTABLISHED


Thanx in advance

Maf wrote:Hi, could anyone explain to me these weird connections created by Ktorrent?
Should I be worried about my privacy?

Code: Select all

maf@firebird ~ $ netstat -n|grep ":... "
tcp        0      1 10.0.0.2:39633          87.16.49.46:161         SYN_SENT
tcp        0      0 10.0.0.2:32833          80.53.72.62:80          TIME_WAIT
tcp        0      0 10.0.0.2:32830          80.53.72.62:80          TIME_WAIT
tcp        0      0 10.0.0.2:60903          80.53.72.62:80          ESTABLISHED


Thanx in advance

The bottom 3 looks like attempts to contact the tracker, 1 succeeded one and 2 waiting to time out.

The top one, if it's indeed from KTorrent, would be an attempt to contact a peer that has yet to respond (half-open connection). It's entirely normal for a torrent client to open numerous connections, that's what is involved in torrenting.

jdong wrote:The bottom 3 looks like attempts to contact the tracker, 1 succeeded one and 2 waiting to time out.

The top one, if it's indeed from KTorrent, would be an attempt to contact a peer that has yet to respond (half-open connection). It's entirely normal for a torrent client to open numerous connections, that's what is involved in torrenting.

Even those low-number ports? Why connecting tracker using port 80? I thought port 4444 is for tracker connections. And once there was a connection with port 21.. why would ktorrent want to connect with this port?

Maf wrote:Even those low-number ports? Why connecting tracker using port 80? I thought port 4444 is for tracker connections. And once there was a connection with port 21.. why would ktorrent want to connect with this port?

Trackers can run on any port. A tracker is nothing more than a fancy HTTP server, which can be configured on any port. Your 4444 is most likely your UDP tracker port, which is different from the standard bittorrent tracker port, which is determined by the tracker field in the .torrent you are downloading.

And as far as low-number ports, I guess that's how the people on the other end have their clients configured. Remember that Windows users typically have free-range access to all ports.

You'd really need to use sudo netstat -anp to figure out first if KTorrent is responsible, then afterwards you might need wireshark to figure out exactly what it's doing on the port, but I bet it's just a peer with a weird port number.

Thanx for the reply