wech Posted October 7, 2006 Report Share Posted October 7, 2006 I don't know if this the way it should be. I just downloaded a 2GB torrent, 15GB actual downloaded data (~13GB junk). My ratio after seeding over 2GB was not 1.xxx but 0.2xx. I wouldn't complain this unless the ratio was updated to the tracker I'm using, and it effected my stat up there. And that means I have to seed ~13GB more to make my ratio on the tracker over 1.Well, I'm happy to seed never less than 1, but this is a bit too much that I have to responsible on junk pieces as well.However, after this incident I've learnt a way to stop junk pieces (probably by spamers). Enable the Protocol Encryption and do not allow legacy connections. By doing so can stop the spamers right away. Link to comment Share on other sites More sharing options...
Ultima Posted October 7, 2006 Report Share Posted October 7, 2006 Protocol Encryption does not prevent torrent poisoning in any way... Link to comment Share on other sites More sharing options...
wech Posted October 8, 2006 Author Report Share Posted October 8, 2006 Well it was just lucky setting then. ~13GB I kept watching this unstopable spam. Several pieces been occupied by ultrafast transfer, then it finished ten or probably more thousand times with hash check failed. And after I turned these settings, using forced encryption with unallowed legacy connection, it just disappeared forever... my luck? I'm not sure Well, what about the ratio thing? Link to comment Share on other sites More sharing options...
Ultima Posted October 8, 2006 Report Share Posted October 8, 2006 Yep, just coincidence/luck if you ask me The ratio thing you can't do anything about, you did download 15GiB after all, and regardless of the fact that a large majority of that was wasted data, the amount was already sent to the tracker =T Link to comment Share on other sites More sharing options...
wech Posted October 8, 2006 Author Report Share Posted October 8, 2006 What is the purpose of encryption protocol then??? Link to comment Share on other sites More sharing options...
Switeck Posted October 8, 2006 Report Share Posted October 8, 2006 Whoever you were downloading from was probably (almost certainly I'd bet) corrupting the torrent on PURPOSE.They don't deserve jack all, because they're WORSE than leeches.Who you were upload TO was only getting your pieces that passed a hash-check. They may have had to suffer getting corrupted pieces from the "infected" peers/seeds, but they too would only share good pieces.I think it's worth a debate whether you can "save" a torrent with 1,000's of corrupters on it with enough good seeds. I really don't know...may depend on how willing people are to manually ban probable bad ip ranges.If protocol encryption SEEMS to help, then use it...but you could leave it enabled and allow legacy connections ...unless you're really getting hit by the corrupters and seem to be hit by NONE of them if using forced encryption and not allowing legacy connections.Try using Peer Exchange if you're not already. You may find more decent peers and seeds to connect to that way. Link to comment Share on other sites More sharing options...
Ultima Posted October 8, 2006 Report Share Posted October 8, 2006 Protocol Encryption is used for bypassing some ISPs' throttling of BitTorrent traffic. Link to comment Share on other sites More sharing options...
wech Posted October 8, 2006 Author Report Share Posted October 8, 2006 I think it's worth a debate whether you can "save" a torrent with 1,000's of corrupters on it with enough good seeds. I really don't know...may depend on how willing people are to manually ban probable bad ip ranges.One thing I found is that this certain, "spammer" or "nuker" or whatever, attacks on a number of certain pieces at a time. After he got auto banned by the program, due to too many failed hash check, he changes his ip and keep on attacking the same pieces again. And this process is really fast that more likely by a program created for this purpose. So I think there is no way that we can just simply ban certain ip's to fix this kind of problem.What I thought I might be right (or wrong), was that by using protocol encryption, it makes thing harder or even imposible for the nuking program to connect to me. And by doing so I can stop him right away. Link to comment Share on other sites More sharing options...
Ultima Posted October 8, 2006 Report Share Posted October 8, 2006 Enabling Protocol Encryption only tells µTorrent to make encrypted outgoing connections, but it still allows µTorrent to make normal outgoing connections. Forcing and disabling incoming legacy connections, on the other hand, makes you use ONLY encrypted connections, but it chews a BIG chunk of potential data sources away from you. Link to comment Share on other sites More sharing options...
Switeck Posted October 8, 2006 Report Share Posted October 8, 2006 It may be the case that the corruptor server farms still lack protocol encryption for the most part -- maybe even because ISPs wouldn't be able (or know) to throttle it.Despite appearances, ussually the address block the corruptors are in are often business-class/commercial ip blocks that are unlikely to be running BT software. I for instance have ALL of 38.x.x.x blocked for this reason...along with lots of other ranges. Link to comment Share on other sites More sharing options...
kihsleek Posted October 12, 2006 Report Share Posted October 12, 2006 Yeah, Switeck is right, as usual. The blocked IP ranges work perfectly. You do it like this:38.xxx.xxx.0-38.xxx.xxx.255208.yy.yy.0-208.yy.yy.255208.zz.zz.0-208.zz.zz.255Well, maybe all of you know this and I'm just messing around... Link to comment Share on other sites More sharing options...
Ultima Posted October 13, 2006 Report Share Posted October 13, 2006 Hm...? What's with those yy.yy and zz.zz stuff...? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.