DHT, Enable or Disable
DHT, or distributed sloppy hash table is used for storing peer contact information for "trackerless" torrents. In effect, each peer becomes a tracker.
DHT has been included with many clients since it first debuted in the summer of 2005. The main problem however, and the reason you are probably reading this is that most people just don’t understand what DHT is, what it does, and how it works.
It's Not really a surprise since the documentation and even the Wikipedia page are filled with technical jargon, and no simple explanation. Without that basic understanding confusion is inevitable.
The easiest way to think about DHT is to imagine it as a form of ‘super tracker’, A large network of peers pass on information requests about torrents without a central server (a private tracker), meaning no control or single point of failure. No information about the contents or even the names of torrents are passed around, a bonus is this makes this legal and hard to shut down.
This however is still a confusing explanation, and there is so much confusion and myths around DHT that this is designed to try and answer some for you.
MYTH: YOU MUST TURN OFF DHT WHEN YOU USE PRIVATE TRACKERS.
Wrong — With the introduction of the private torrent function in 2008 and the global adoption of this feature by early 2009 the element of a private torrent that is called the ‘private flag’ is utilized. It’s a small flag that marks to a client that the torrent is ‘private’ and disables any method of sharing peers (including DHT), except via the tracker. This flag also changes the hash, so peers on a non-flagged torrent could not connect to a flagged torrent in any case.
When a BitTorrent client obtains a metainfo file (Torrent file) containing the "private=1" key-value pair, it MUST ONLY announce itself to the private tracker, and MUST ONLY initiate connections to peers returned from the private tracker.
Most private torrent sites check for the flag, and add it if missing when the torrent is initially uploaded to their site, Meaning DHT will not work on these torrents.
MYTH: CERTAIN CLIENTS LEAK DHT DATA AND SHOULD BE AVOIDED.
Wrong (with one exception) — There are always going to be people that want control. When it comes to torrent sites (especially the private ones) they like to express their control through lists of clients you can and can’t use (a form of DRM) and sometimes give reasons to support this. An example would be this statement from a staff member at a private tracker:
This statement is completely false. All torrent clients that support DHT respect the flag. The flag is set by the torrent file, not the tracker (although the tracker can add the flag to the file, it’s still set by the torrent), and BitComet does NOT ignore the flag. The one exception is a single build of BitComet (0.60) that was available for 2 weeks at the end of 2005, and even then, was a fallback only if the tracker was unable to be contacted for a 30minute period. Bitlord is unable to leak to DHT, as it doesn’t use DHT at all, NOTE: The Private Flag was not introduced as a standard at this time anyways.
If you see staff making claims like this, it’s a good indication that the staff is clueless, which might be an idea to leave that tracker. If they can’t get the basics right who knows when else is wrong.
MYTH: YOU CAN BE TRACKED BY DHT / ANTIP2P GROUPS USE DHT TO FIND YOU
Unlikely — It’s much easier and simpler to use the tracker. Blocklists, used on your client and on the trackers, are generally ineffective and easily circumvented through the use of residential connections. Last year’s University of Washington study showed that they will send letters just based on tracker info.
MYTH: DHT SLOWS YOUR SYSTEM DOWN
Generally not true — It can slow down your connection depending mainly on network hardware. The actual data used in running DHT is low, generally less than 1kilobyte a second. Some routers and modems, however, can have problems with DHT causing lockups and restarts if they run out of ram. This mostly happens with lower spec ‘home’ equipment (such as older Belkins, Netgears and D-links), or telco-provided hardware, this is not something that would affect a user with the modern and enterprise level equipment that AppBoxes is using
MYTH: YOU NEED TO CONNECT TO A TRACKER, BEFORE YOU CAN USE DHT
Wrong — When DHT is enabled (certainly in uTorrent) it connects to a bootstrap node (such as router.utorrent.com or router.bittorrent.com for mainline, or dht.aelitis.com for Vuze) and uses that to enter the DHT ‘swarm’. It’s handed a set of DHT nodes and uses that to build up a small group of connected nodes. Those nodes are then used to get peers. No tracker is required at any time.
MYTH: WHEN ENABLED, IT SENDS USAGE DATA BACK TO [INSERT COMPANY]
Wrong — This is another case of people not knowing what they’re talking about. Generally they’re misinterpreting the bootstrap node connection for their client.
When the demonoid tracker was finally resurrected last year, many of it’s torrents were still active thanks mainly to DHT. DHT with Peer Exchange (PEX) is a very powerful addition to the torrenting world, and allows torrents to stay active, irrespective of the trackers stability or even existence. Also, Azureus/Vuze users, despite having their own DHT system, can join in using a mainline DHT plugin.
Should you use DHT? If you only use private trackers it has not effect to you, but if you use public ones, then yes. It can help reduce tracker load.
User Submitted - Zycore
We've setup a chat system on one of our AppBoxes so you can get status updates and hangout with other users and ourselves, feel free to ask anything and maybe the community will be able to provide further support.