Mystery Revealed : Why trackers/seeds ban BitComet..

[ComradE_BeaN]

Lets start with how the Peers receive from a Seed.

When a Super-Seeder is connected to some peers...(super-seeding mode is best when there is a single Seed ) the Azureus connects & distributes the pieces in this order...

peer1| peer2|peer3|peer4|peer5|peer6......

piece1|piece2|piece3|piece4|piece5|piece6..........

This is to ensure that the pieces sent to one peer is redistributed to others from the peer...this is how the Torrent is originally supposed to run..
When this distribution of 1-->n is in progress...the client checks about the availablilty of the already distributed pieces in the swarm..

By determining which peer is distributing the pieces better, the priority is given to the peer.... sounds well doesnt it...:bleh:

But here is the dirty part what BitComet does . . some version are reported to disconnect to the seeder after a timedelay/specified ( there are hacks for this.which i wont talk abt now)
So when the BC client disconnects & reconnects to the seed.the seed thinks of the peer as NEW & distributes newer pieces....:S

This ends up Bitcomet users getting faster download speeds .. . .. & it is also true that most of the Leechers User Bitcomet..

This is the MAIN reason why Bitcomet is banned in most of the private trachers...

& yeah... i also kick & block all the BC clients from my Azureus when i'm seeding & super-seeding..:cool2: hyeah:

This is the reason some get some better speeds with BC than other clients..

To kick & ban BC users..i use this plugin for Azureus
StuFFeravailable @ Azu website.
reason 2...
Even when there are good seeds & peers the comet can do tricks that can void the private tracker information to open..i.e, leeching

Private trackers are not looking to widely distribute their files. These communities are designed to only allow private sharing by locking each registered member’s account to an IP address - or if the individual has the correct passkey. In addition, a ‘private’ flag within the torrent file tells the BitTorrent client not to share on the DHT network.

However, many private tracker operators argue that BitComet does not honor the private flag. Instead, the torrent is shared on the DHT network and those who do not belong to the private tracker can freely leech off the resources of that community. That is the much simplified story many private trackers are telling.

Yet many are not so quick to blame BitComet. BitComet does share private torrents, but only when certain conditions are met. In order for BitComet to share torrents, the following must happen.

An individual (person "A") who belongs to a private tracker downloads a torrent. The torrent contains the necessary peer information (such as IP addresses) to initiate the swarm. Person "A" then uploads the private torrent to a public tracker such as Mininova.org. Person "A's" IP address, along with private peers, are contained in the torrent file.

The private tracker must be completely unreachable. Person "A" can achive this by simulating a site outage (for example, by altering the host file.) But for our purposes lets assume the private tracker is suffering a DoS attack and is unreachable for an extended period.

The BitComet client will eventually give up trying to reach the private tracker and enables the DHT network.

At this point, and only at this point, will outsiders be able to access the torrent shared over the DHT network. When the torrent is downloaded, the client will connect to the peers in the DHT network - providing the outsider cannot access the private tracker, and has DHT enabled.

Contrary to popular belief, the torrent file isn't freely shared on the DHT network. Only those who are identically configured can take advantage of the private torrent.

Never the less, this is highly frowned upon in private communities. To ensure sharing and save bandwidth, many trackers have tight download/upload ratio policies and enforce them strictly. Since the neither the DHT network nor BitComet have any concept of ratios, the torrent is traded freely. This situation has especially been a kick in the µTorrent for those donating to private trackers in return for higher status and more privileges.

The solution? Ban BitComet

no problemo to me....a Azureus user..

 

[-nsan-ty]

But dwloads continue on BitComet 0.67, myself using it, as a suggestion of the TE members hyeah:
Though the speeds arent that special, but i was really impressed with the rich UI of BC :hap2:

eah... i also kick & block all the BC clients from my Azureus when i'm seeding & super-seeding..

LOL, i ban any ip that's having a faster dwload rate than mine, and is also uploading from me

 

[scarezebra]

Hey Thanx for the info..Always wanted to know y BitComet was being banned, but wa too lazy to find out....Me using utorrent..Anyway for blocking BC users in utorrent?

 

[ComradE_BeaN]

But dwloads continue on BitComet 0.67

all the version can get blocked....so

@scarezebra : i dunno if there is a addon or options to block certain type of clients...&after using Azureus & playing with its' setting...i dont feel like using anyother client...:cool2:

 

[chic_magnet]

hmm ya i still use bitcomet for public downloads.... for private ones i use abc/bit-tornado.. i love azureus too esp the rss feature.. but then whats the use ? i dont have unlimited.... so well i dont use azureus much. except when i have to make a torrent :bleh:

actuallyi have hardly used azurues since my dial days.. its still bittornado for me...

 

[dipdude]

About first part of your post -

Those some versions you are talking about are hacked versions of bitcomet - nothing to do with official releases, and those things can be implemented in other p2p applications too...so its not only bitcomet which is at fault - its the users who are to be blamed for using hacked applications.

About 2nd part -

The DHT & private flag bug has been sorted out in later versions of bitcomet 0.6x, bitcomet is not banned from any tracker at the moment including private trackers.

---------

This is a old story which has turned into a urban myth, next time please quote the source of your article or recheck the date of the source, as all this has been rectified iirc.

My humble advice is move onto bitcomet, you wont regret it

 

[-nsan-ty]

How'd u differentiate between private trackers and public trackers?

 

[dipdude]

^ Private trackers would not allow you to download without first registering at their site... case in point idesir, torrentleech.org, oink.me.uk etc.

They have some kind of hash/pass key added to their trackers - the pass key would be unique for each & every user & only valid keys would be allowed to download/upload a file.

Also they usually maintain a db of your uploads & downloads, anytime you break their U/D ratio they would knock you out. Also they can implement a queue system where preference would be given to users having a healthy U/D ratio or are VIP members etc.

 

[ComradE_BeaN]

^it is not very old..i typed the first part myself...second part i had somewhere in my documents...
there are some private trackers..which have started blocking BC just recently since a few days....also..there are multiple hacks thru which u can change the ID of your client....in indeed proves how many sites are blocking BC..

 

[Kumar]

AFAIK,the only site i know of still having probs with BC is bwtorrents.My ststs with BC aren't updated as they should.

OT:MAH 800th POST!!!

 

[chiron]

is bitlord based on bitcomet?

 

[Kumar]

This is taken from one of the private trackers I use.

# Banned Clients

# ABC - randomly reports bad stats to the tracker
# BitLord - based on old buggy BitComet code.
# burst! - no longer maintained
# eXeem - not a proper Torrent client.
# Shareazza - not a proper Torrent client.
# G3 - consistantly reports bad stats to the tracker
# BitSpirit - randomly sends DHT packets to its own public tracker
# eDonkey2000 - not a proper Torrent client.
# Turbo Torrent - rumoured to do bad things
# BinTorrent - users caught cheating with this client
# Torrentstorm - development and bug fixes ceased 30th March 2005.
# BitComet - very very popular client but EVERY version reports bad stats to the tracker and many leak to DHT.
# XBT Client - by default does not identify itself on the swarm or can be configured to pretend to be another client.
# Qtorrent - Does not identify itself correctly and gets caught by another client ban.
# Bittorrent++ -
# CTorrent and clones - communicates with the tracker incorrectly (aka not following BT spec)
# ed2k - not a proper Torrent client.
# MLdonkey - not a proper Torrent client.
# Opera - not a proper Torrent client.
# Torrent Station - Does not uniquely dentify itself.
# Ziptorrent - does not identify itself correctly (specifically it lacks version number).Being used principaly by spoofers, taking advantage of this bad code decision.
# Acquisition - not a proper Torrent client.
# Rufus - constantly reports bad stats to tracker
# ktorrent - sends bad stats to the tracker

Source

Actually BitComet from ver 0.64 is clean.

 

[ComradE_BeaN]

^^but when someone blocks a particular client....very rarely do they check for the versions.....BC is no doubt the top of the list among banned clients...

 

[Kumar]

yes,they DO check for the versions.Bitcomet v0.6 was the culprit and it was banned till ver 0.64 fixed the problem.

This was from the torrentleech FAQ

Most common reason for stats not updating

The user is cheating. (a.k.a. "Summary Ban")

The server is overloaded and unresponsive. Just try to keep the session open until the server responds again. (Flooding the server with consecutive manual updates is not recommended.)

You are using a faulty client. If you want to use an experimental or CVS version you do it at your own risk.

You are using BitComet that has peer caching and peer sharing abilities (and you are downloading torrents from other trackers too) In this case, your clients uses sources from peers that are not members of our tracker and not connected on our tracker, so the traffic downloaded/uploaded from/to them is not counted in your stats.

We suggest to all users to use well tested clients like Azureus, ABC (not edition 3), BitComet (using the patch that disables peer sharing) in order not to have problems.

Torrentleech FAQ

 

[ComradE_BeaN]

yes ,most of the private trackers ask the members to block the peer sharing...i'm surprised they have a patch for BC to do that...geez doesnt it have it as a option..?There are soo many plugins & options in Azureus..i have to admit i somtimes lose track where i did the changes,,,,

but seriously n00bs dont give a damn abt all these do they...signup, leech as much as possible (ofc forgetting to turn off peer sharing )& start crying why they arent getting any speeds . . .
i partially agree tough..the users are to be held responsible .

was searching for smthing in google when i came across a patch for BC v6.** to give it a user defined identity...now how sick is that...
maybe there are undercover BC users with tags of utorrent,azureus too . .
:S (now dont ask me for the patch ,never downloaded as i never use BC )

 

[Kumar]

I agree with u on that,but IMHO,BC is one of the best clients out there (Azereus ,even in itself is quite efficient,the associated jawaw.exe takes up huge resources,utorrent doesn't give good speeds for me atleast.)

 

[chic_magnet]

bit-tornado.. shadow's experimental client is also another recommended torrent client by many registered sites...

personally its my fav. dunno its just that i`ll always get full speed using tornado then i would using azureus or bit comet... esp if the torrent needs a bit of "upload" pampering lol.

use abc if i have multiple torrents.. for downloads and uploads.. and bitcomet for public trackers

 

[shirish]

I don't know what good speeds are or aren't on my BSNL 256 Kbps utorrent gives me 24/25 Kbps uploads & 4/5 Kbps upload 4:1 ratio. Don't know what other clients speeds are giving.

 

[shirish]

Private trackers are not looking to widely distribute their files. These communities are designed to only allow private sharing by locking each registered member’s account to an IP address - or if the individual has the correct passkey. In addition, a ‘private’ flag within the torrent file tells the BitTorrent client not to share on the DHT network.

:hijack: Interesting in the Indian context of dynamic IP's most of the time I think passkey is the variable. But each time how does it know to give passkey to the right individual (individual). Here I think there's a software fingerprint/checksum which is made which might include the Lan card MAC address or something like that. Has anybody figured that part out?

Secondly where can u see the private flag in the file. AFAIK one can only tell it's a private file if the tracker info space also has a passkey there.

Never the less, this is highly frowned upon in private communities. To ensure sharing and save bandwidth, many trackers have tight download/upload ratio policies and enforce them strictly. Since the neither the DHT network nor BitComet have any concept of ratios, the torrent is traded freely. This situation has especially been a kick in the µTorrent for those donating to private trackers in return for higher status and more privileges.

How are download/upload ratio policies maintained. Are they maintained for their files only or with the overall picture? I use utorrent & the client does produce some statisitics. Are these statistics used by the private tracker to see how good/bad a sharer I'm or it looks for only the files I've been downloading from them?

 

[Kumar]

Passkeys r not based on IPs.
From Oink

Now, when you download a .torrent file, you get a different file than everyone else gets. The difference is in the tracker URL contained in the .torrent file. It now looks like:

http://tracker.oink.me.uk/tracker/your_passkey/announce

Your passkey is a random set of 16 characters, guaranteed to be unique to you. It's stored in your user details and can be used to discover your identity. Now, we no longer need to use your IP address to figure out who you are. The .torrent file itself contains your identity. There aren't any problems with mixing of stats and no more need to permanently store IP addresses on the server.

The current tracker is more sophisticated in other ways as well. If your IP address is dynamic, the new tracker will keep track of it and send your updated IP address to others in the torrent. In order to protect the privacy of our users, seeders will no longer be given the IP addresses of other seeders (they ignore them in any case). If there are attempts to take over your session by someone "spoofing" with your peer_id, the new tracker uses the relatively new BitTorrent key to prevent them. It's more efficient in other ways, like not sending a list of peers if your BT client specifically asks that none be sent. It supports no_peer_id and compact mode, saving us bandwidth. It works better with Azureus, supporting both multiple scrape and scrape within an announce.

So,no matter where you are,the tracker can keep track of ur data.