This is an old revision of the document!
Refer to this post in our forum to follow the step-by-step guide.
Rubbish data or garbage data, is a term used to describe, in the BitTorrent scene, downloaded pieces which failed to pass the hash-check and consequently are discarded. They are regarded as garbage since they are of no use to the downloading client and only waste bandwidth and time.
Possible causes
Solutions
1. The only solution, so far, to this problem is to download Peer Guardian: http://phoenixlabs.org.
Download and install the client, and when it comes to the screen of 'Updates' click on the check-boxes: Government, P2P, Ads. Then let PeerGuardian update its lists. Allow PeerGuardian to run every time your BitComet client is functioning. This may reduce, in some cases, the amount of garbage data you get, by refusing connections to some IPs known to interfere with P2P downloading.
A reminder to users: This program does not guarantee that you will receive nil rubbish data, or that you'll be “protected” from governmental agencies trying to obtain your IP address. A lot of users are under the general false idea that some programs are able to block all rubbish data or conceal them on the P2P networks; we can assure you that this is not true. The most that it can do is limit the amount of rubbish data being passed through to your torrent client.
However, whenever you use Peerguardian or Protowall alongside any P2P applications, be aware that if you configure it improperly, it may limit your download capability, especially for torrents that have peers in some of the ranges you might have chosen to block (such as educational institutions - university campuses).
2. In order to verify if your router is the cause of your trouble, you should try and take the router out of the loop, if possible, or if the modem and router are integrated try to replace it for testing purpose. Then run your BitTorrent client for a while and check if you get the same average amount of garbage data (some rubbish data may still come for reasons described in paragraph 1).
Also you might try updating your router's firmware in order to see if that helps you get rid of the problem. If that doesn't cut it, you might consider changing your router.
The difference between Private Trackers & Public Trackers.
It's important to understand that BitTorrent is a network completely different from FastTrack (clients: Kazaa, Grokster, Morpheus, iMesh etc.) or Gnutella (clients: Shareaza, Limewire etc.), in the respect that people who download a torrent must at the same time upload data to other peers, and the most fundamental rule of all torrents is: The higher your upload capability is, the better your download capability will be. That is, as far as the rest of the swarm is concerned; granted, of course, that your client is properly configured as well. [For more information on how to maximize your download speed with BitComet, please read our Speed Guide.]
Public trackers are tracker URLs which are made public, or in other words, torrents with this type of tracker allow ALL users to both access and download this torrent's contents. As a result:
i.e.: isohunt.com, torrentspy.com, mininova.org
Private Trackers are tracker URLs which are private, users must register at their home site to be able to access both this site's torrents and tracker:
i.e.: Filelist.org, Midnight torrents, etc. [Search via Google - Private torrent community/site]
In my trackers –> Status tab, I'm seeing errors like Can't connect to tracker (110004), waiting 1800s to retry, or Can not resolve host address [Shown below]:
Solution
Unfortunately there isn't any solution to this issue, because it is the tracker itself that's down or unavailable. Try stopping and restarting the torrent download, to try and re-connect to the trackers. If the trackers are all unresponsive, be sure to use the DHT network to connect to peers [Right-click on the torrent –> Properties –> Advanced –> click the checkbox Enable DHT network].
If your Internet connection is configured to redial if the line is dropped (meaning if your Internet connection disconnects, it will automatically re-dial by itself), and if your Internet does indeed disconnect, and redial by itself, BitComet may be unable to connect to these trackers. This can be resolved by disabling your Internet Connection, and re-enabling it, then opening BitComet to resume the downloads.
If the tracker gives the status: “Can not resolve host address.” Then this is mainly because you're using BitComet's UDP trackers, these rarely work unfortunately. Try using public trackers such as
Registration at Demonoid.com and torrentbox.com will also allow you to use their torrent trackers.
BitComet's UDP trackers are usually only used for uploading BitComet torrents (e.g. setup files, etc).
The easiest way is to “Drag & Drop” the file or directory to the BitComet window. You can also go to File » Create a Torrent… (Ctrl+M), or Hit 'Maker' in the toolbar. All these bring up the “Make Torrent” GUI.
Fill in the fields.
Hit OK. Start seeding the task.
Note: When you have made a .torrent file, you must publish the torrent on a torrent index site. And please make sure BitComet is started and seeding the task, so that others can download from you once they saved the .torrent file.
For more info see Making torrents with BitComet.