Login Issue? Delete D-addicts cookie from your browser settings and login again.

Question re peer stats

Read the FAQ in here first then post your questions here if it doesn't help you.
Post Reply
debuf
Posts: 16
Joined: Mar 8th, '09, 12:28

Question re peer stats

Post by debuf » Jul 30th, '09, 01:26

The "peer stats" accessed by clicking on the "show peer stats" link on torrent pages always show the following peer:
Peer IP Uploaded
a z Downloaded
a z Progress
a z Connected
a z Share Ratio
a z Average Upload Rate Average Download Rate
85.17.170.xxx 100 B 100 B 670.60 MB (100%) 0d 00:43 1.000 0 B/sec 0 B/sec
85.17.170.xxx 100 B 100 B 670.60 MB (100%) 0d 00:13 1.000 0 B/sec 0 B/sec
85.17.170.xxx 100 B 100 B 670.60 MB (100%) 0d 00:31 1.000 0 B/sec 0 B/sec
What peer is this? Do these represent connections to the tracker?

(I've suggested in this thread that these listings not be included as "DL" peers in torrent stats.)

User avatar
peacht
Global Moderator
Global Moderator
Posts: 865
Joined: Dec 29th, '04, 14:46
Location: UK

Post by peacht » Jul 30th, '09, 07:44

If you google this ip you'll see that it's not only happening here. Each search result shows a different tracker where this peer shows the same behaviour.

User avatar
groink
Posts: 2016
Joined: Dec 8th, '03, 03:58
Location: Pearl City, Hawaii

Post by groink » Jul 30th, '09, 08:53

Some information regarding 85.17.170.xxx...

Apparently, the subnet is owned by Leaseweb. Leaseweb is known to be a organization that hosts macro BitTorrent trackers - including biggies at one time like Demonoid and everlasting.nl. I suspect that you see them connecting everywhere as a means of indexing the entire world of BT trackers and torrents.

Indexing sites basically index trackers several ways. One way is to scrape torrent information using the announce feature of a tracker - but this is only a snapshot. The more advanced indexers will modify a BT client like uTorrent, and report 100-percent completion to everyone in the swarm for a given torrent. This would then cause all the leechers to contact the fudged BT client, and real-time data can then be gathered - including the leechers' IP information, torrent performance like speed, etc.

I'd firewall the entire 85.17.170.x block if I ever ran across it.

--- groink

debuf
Posts: 16
Joined: Mar 8th, '09, 12:28

Post by debuf » Jul 30th, '09, 13:04

I googled the IP and yes, it seems to be happening all over the place. It's interesting that the only talk I could find about it was here at d-addict. Here's another d-addict thread re that IP. I don't know much of the technical aspects of this stuff, but "y'a gotta wonder"....

Can't the d-addict tracker block the IP? It doesn't seem to be engaging in torrent activity and it's screwing up the stats...

I've also found instances where other ips have multiple listings in the stats, but are showing various levels of completion and connection times. Here are a couple of the same client (there are several more instances involving the same client):
Name: Yi.San.E20.071120.HDTV.XViD-Ental.avi

* * * * * * * * *

Leechers (6)

Peer IP Uploaded
a z Downloaded
a z Progress
a z Connected
a z Share Ratio
a z Average Upload Rate Average Download Rate
85.17.170.xxx 100 B 100 B 670.60 MB (100%) 0d 00:19 1.000 0 B/sec 0 B/sec
85.17.170.xxx 100 B 100 B 670.60 MB (100%) 0d 00:43 1.000 0 B/sec 0 B/sec
66.8.164.xxx 0 B 822.93 KB 417.00 MB (63%) 0d 00:14 0.000 0 B/sec 957 B/sec
66.8.164.xxx 0 B 0 B 416.00 MB (63%) 0d 00:20 0.000 0 B/sec 0 B/sec
66.8.164.xxx 0 B 0 B 415.00 MB (62%) 0d 00:21 0.000 0 B/sec 0 B/sec
66.8.164.xxx 0 B 0 B 413.00 MB (62%) 0d 00:47 0.000 0 B/sec 0 B/sec
Generated in 0.000 seconds.
Name: Yi.San.E24.KOR.HDTV.XviD-Ental.avi

* * * * * * * * *

Leechers (6)

Peer IP Uploaded
a z Downloaded
a z Progress
a z Connected
a z Share Ratio
a z Average Upload Rate Average Download Rate
85.17.170.xxx 100 B 100 B 686.91 MB (100%) 0d 00:15 1.000 0 B/sec 0 B/sec
85.17.170.xxx 100 B 100 B 686.91 MB (100%) 0d 00:40 1.000 0 B/sec 0 B/sec
66.8.164.xxx 0 B 0 B 34.00 MB (5%) 0d 00:03 0.000 0 B/sec 0 B/sec
66.8.164.xxx 0 B 0 B 34.00 MB (5%) 0d 00:12 0.000 0 B/sec 0 B/sec
66.8.164.xxx 0 B 0 B 34.00 MB (5%) 0d 00:38 0.000 0 B/sec 0 B/sec
66.8.164.xxx 0 B 0 B 34.00 MB (5%) 0d 00:05 0.000 0 B/sec 0 B/sec
Generated in 0.000 seconds.
Each of these are also counted as a "DL" peer.

Any idea what's up with that, groink?

User avatar
groink
Posts: 2016
Joined: Dec 8th, '03, 03:58
Location: Pearl City, Hawaii

Post by groink » Jul 30th, '09, 22:57

debuf wrote:Any idea what's up with that, groink?
What I find interesting is that I experienced the multiple connections by 85.17.170.xxx when I ran BitComet. At one time, BitComet was eating a huge amount of bandwidth, and it brought my ethernet hub to a crawl! So I quit BitComet, closed all the connections using a TCP tool, and then ran uTorrent on the exact same torrent. The problem and the 85.17.170.xxx user went away!

Something worth trying on your end.

--- groink

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests