Jump to content

Ban peers who continuously send bad data !


knotty

Recommended Posts

Could this be implemented into µtorrent ,its already in bittornado ,but thats not as good or efficient as µtorrent .Basically if some peer continually sends you bad ,unuseable data ,then the client simply kicks them off , no selective banning is involved ,just the actual bad data sender .Dloaded a 2 gb torrent to find 5 hash fails and 148 mb of wasted data also sent .If the offending peer is removed from the torrent dload it will save you time dloading worthless data ,and speed up your finish time as well .It is user selectable in tornado and would be good to have the same choice for µtorrent as well . :)

Link to comment
Share on other sites

A recent torrent i downloaded had in excess of 170 hash failures also (~0340MB of data), in my experience, these hash failed pieces were bad/corrupt/fake data... I looked in the peer-list and a lot of the peers i was transferring data from were in the same IP-Block range... So suspicions were aroused.. And i decided to install Protowall, I then re hash-checked the torrent, rebooted, update the IP block list in Protowall, and continued to download the torrent.... It finished shortly after (which was a surprise to me, because the % completed fluctuated so much (obviously) because of the amount of failures) and none of the same IP-Block range IPs were present, but Protowall was throwing a right fit

Guess that explains a lot for that torrent anyway :)

Link to comment
Share on other sites

  • 2 weeks later...

Well done kludge, infact most bad data comes from fake seeders. You can see this when you try to download the latest file movies.

The following fucntions are usefull.

Auto ban peers which keep sending bad data

1 IP per task for uploading and downloading ( sometimes you have 1 IP with many ports connecting to you to download 1 torrent it most likely a fake peer trying to waste you banwidth)

built in Auto safepeers like Azureus whcih auto updates untrusted IP range everytime it you start a uttorent. Currenlty Utorrent uses IPfilter.dat not sure how effective it is.

BTW here the known MPAA IP range and fake MPAA trackers. These bastards can delay you from getting a 1gb file for up to 76 hours. I got hit once now I uses Azureus but haven't tried uttorent yet, I'll get a try and see.

38.112.0.0 - 38.119.255.255 (Performance Systems International Inc)

64.34.160.0 - 64.34.191.255 (ServerBeach, Peer 1 Network Inc)

64.62.170.0 - 64.62.170.255 (Peak Web Hosting)

64.124.0.0 - 64.125.255.255 (Abovenet Communications Inc)

66.250.46.0 - 66.250.47.255 (MediaSentry/SafeNet)

70.84.0.0 - 70.87.127.255 (ThePlanet.com Internet Services)

168.215.129.64 - 168.215.129.95 (MediaSentry)

206.169.170.240 - 206.169.170.255 (MediaSentry)

206.169.225.80 - 206.169.225.95 (MediaSentry)

206.169.230.96 - 206.169.230.111 (MediaSentry)

208.50.192.0 - 208.51.255.255 (Global Crossing)

209.203.99.224 - 209.203.99.239 (MediaSentry)

The myBittorrent.com Staff has identified the following trackers as BAD TRACKERS: most must have change by now

http://distan.servecounterstrike.com/announce

http://freevideo.no-ip.info/announce

http://zorba.zapto.org/announce

http://fuf.zapto.org/announce

http://tzar.servecounterstrike.com/announce

http://whypay.servebeer.com/announce

http://m0vies.servep2p.com/announce

http://matha.sytes.net/announce

http://tracker.workisboring.com/announce

http://freemovies.serveftp.com/announce

http://chech.servequake.com/announce

http://kur.servegame.com/announce

http://nia.servehttp.com/announce

http://torrentsource.servemp3.com/announce

http://mpaa.servehttp.com/announce

http://nopay.no-ip.info/announce

http://prince2.bounceme.net/announce

http://startracker.geekgalaxy.com/announce

http://cash.servequake.com/announce

http://gleneagle.damnserver.com/announce

http://zesty.no-ip.info/announce

http://206.81.133.67/announce

http://coolserver.servecounterstrike.com/announce

http://mpaa.servehttp.com/announce

http://tracker101.no-ip.info/announce

http://q1.sytes.net/announce

http://matha.sytes.net/announce

http://mishmish.servemp3.com/announce

http://waikiki.net-freaks.com/announce

http://only-guiness.servebeer.com/announce

http://gruzia.zapto.org/announce

Link to comment
Share on other sites

damn, theres a lot of fakery around... Shame some people are too ignorant, or unknowing and blame the client :)

That instance above was with AZ, and i could easily manually kick the peers... µTorrent doesn't have that `feature`, but in all fairness even with protowall running i still got a lot of bad peers with µTorrent...

Still, almost every time i'm using µTorrent now, just occasionally having to resort to the bloatware that is AZ... And its pretty painful watching my system get chewed up when obviously it needn't be... Just goes to show!

:w00t: for team µTorrent

:thumbsdown: for team AZureus.. You're getting sloppy

Link to comment
Share on other sites

I'm on a small swarm, and I've noticed two peers that keep sending bad data. Both get up to 5, disappear, then come right back. They're both Comcast IP's. It seems µTorrent blocks them, but then they come right back, get up to 5 hash errors, disappear again. Same IPs, over and over.

-Ares

Link to comment
Share on other sites

It was stated that Peer Guardian was not relevant to this discussion but PG can be used to block an individual IP by creating an additional list of your own creation and adding the offending IP to it; you have to state it as a range of IPs, so just use the same IP for the first and the last in the range. It's a little bit of work to do so but it's effective.

If anybody needs a step-by-step, I could post one.

:-)

Link to comment
Share on other sites

Actually I seem to be getting bad data from Comcast peers in almost all my torrents (which are from the pointy-eared pitchfork-bearing little green guy tracker). And after 5, they disappear, only to return again. Over and over, the *same* IP's per torrent.

-Ares

Link to comment
Share on other sites

Actually I seem to be getting bad data from Comcast peers in almost all my torrents (which are from the pointy-eared pitchfork-bearing little green guy tracker). And after 5, they disappear, only to return again. Over and over, the *same* IP's per torrent.

-Ares

Maybe you can use PG to block them as a group - find the lowest and highest IPs from the group and create a personal block list, then add a blocked range (from lowest to highest) and they should never appear again in µTorrent.

Link to comment
Share on other sites

@atkerr: Unfortunately I also have a lot of Comcast users who send good data. If I block Comcast, I lose a lot of legitimate peers. There should be a way to permanently ban a peer (per session, per torrent) after X amount of hash fails. It's not enough to just boot them out and let them back in again.

-Ares

Link to comment
Share on other sites

client depending, it will tell you, in AZureus its in the details of the torrent, it will tell you how much data you've discarded (thrown away because your client didnt ask for it) hash-fails, number of times the piece size, and total (this will be the biggest indicator) :)

Not looked into µTorrent so much, I just leave it running now, unattended.. absolute bliss too! :D

Link to comment
Share on other sites

will have to check that out if/when my torrent box eventually crashes, thanks Firon LOL! 4 weeks uptime, no stagnant connection or anything... µTorrent is so transparent i wouldn't know its running apart from the noisy CPU fan... Need a better one, this crappy motherboard goes by core temperature rather than surface temperature :(

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...