Unmatched incoming bittorrent connections.

Brought to you by: raboofje

#19 Unmatched incoming bittorrent connections.

Milestone: v1.0 (example)

Status: closed-fixed

Owner: nobody

Labels: None

Priority: 5

Updated: 2016-01-01

Created: 2012-03-01

Creator: Anonymous

Private: No

If I am using rtorrent listening on port 9000. I see many incoming connections assigned to root with no program that are obviously rtorrent.

Discussion

Arnout Engelen - 2012-03-08

Do you see those exact incoming connections in netstat?

I'm not entirely certain, but I believe bittorrent uses a lot of short-lived connections. It might be the connection disappeared from /proc/net/tcp before nethogs had a chance to take a look at it.

If you see the connections in netstat, something else is going on.

Not sure how to debug this. We should probably create a test tool that simulates traffic based on a wireshark dump you can create. Can you make a small test running 'nethogs -b' and capturing the output and the corresponding traffic in wireshark?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Arnout Engelen - 2012-03-13

summary: Incoming connections. --> Unmatched incoming bittorrent connections.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Arnout Engelen - 2013-05-12

status: open --> pending-fixed

Group: --> v1.0 (example)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Arnout Engelen - 2013-05-12

Can you try the latest CVS version? It should be more forgiving about short-lived connections like bittorrent uses.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Arnout Engelen - 2016-01-01

status: pending-fixed --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link: