Jump to content
 







Main menu
   


Navigation  



Main page
Contents
Current events
Random article
About Wikipedia
Contact us
Donate
 




Contribute  



Help
Learn to edit
Community portal
Recent changes
Upload file
 








Search  

































Create account

Log in
 









Create account
 Log in
 




Pages for logged out editors learn more  



Contributions
Talk
 



















Contents

   



(Top)
 


1 Public vs private trackers  



1.1  Public trackers  





1.2  Private trackers  







2 Legal issues  





3 Legal uses  





4 Improving torrent reliability  



4.1  Multi-tracker torrents  





4.2  Trackerless torrents  







5 IPv6 support  





6 Software  





7 See also  





8 References  














BitTorrent tracker






العربية
Български
Ελληνικά
Español
فارسی
Français

Italiano
Nederlands
Norsk bokmål
Português
Русский
Slovenščina
Svenska
Українська

 

Edit links
 









Article
Talk
 

















Read
Edit
View history
 








Tools
   


Actions  



Read
Edit
View history
 




General  



What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Cite this page
Get shortened URL
Download QR code
Wikidata item
 




Print/export  



Download as PDF
Printable version
 




In other projects  



Wikimedia Commons
 
















Appearance
   

 






From Wikipedia, the free encyclopedia
 

(Redirected from Torrent tracker)

ABitTorrent tracker is a special type of server that assists in the communication between peers using the BitTorrent protocol.

Inpeer-to-peer file sharing, a software client on an end-user PC requests a file, and portions of the requested file residing on peer machines are sent to the client, and then reassembled into a full copy of the requested file. The "tracker" server keeps track of where file copies reside on peer machines, which ones are available at time of the client request, and helps coordinate efficient transmission and reassembly of the copied file. Clients that have already begun downloading a file communicate with the tracker periodically to negotiate faster file transfer with new peers, and provide network performance statistics; however, after the initial peer-to-peer file download is started, peer-to-peer communication can continue without the connection to a tracker.

Modern BitTorrent clients may implement a distributed hash table and the peer exchange protocol to discover peers without trackers; however, trackers are still often included with torrents to improve the speed of peer discovery.[1]

Public vs private trackers[edit]

Public trackers[edit]

Public or open trackers can be used by anyone by adding the tracker address to an existing torrent, or they can be used by any newly created torrent, like OpenBitTorrent. The Pirate Bay operated one of the most popular public trackers until disabling it in 2009 due to legal trouble, and thereafter offered only magnet links.

Private trackers[edit]

Aprivate tracker is a BitTorrent tracker that restricts use by requiring users to register with the site. The method for controlling registration used among many private trackers is an invitation system, in which active and contributing members are given the ability to grant a new user permission to register at the site, or a new user goes through an interview process.[2]

Legal issues[edit]

Legal uses[edit]

There are several circumstances under which it is legal to distribute copyrighted material or parts thereof.

There are also experiments that legally sell content that is distributed over BitTorrent using a "secure" tracker system.

Improving torrent reliability[edit]

Trackers are the primary reason for a damaged BitTorrent "swarm". (Other reasons are mostly related to damaged or hacked clients uploading corrupt data.) The reliability of trackers has been improved through two main innovations in the BitTorrent protocol.

Multi-tracker torrents[edit]

Multi-tracker torrents contain multiple trackers in a single torrent file. This provides redundancy in the case that one tracker fails, the other trackers can continue to maintain the swarm for the torrent. One disadvantage to this is that it becomes possible to have multiple unconnected swarms for a single torrent where some users can connect to one specific tracker while being unable to connect to another. This can create a disjoint set which can impede the efficiency of a torrent to transfer the files it describes. Additional extensions such as Peer exchange and DHT mitigate this effect by rapidly merging otherwise disjoint graphs of peers.

Trackerless torrents[edit]

Vuze (formerly Azureus) was the first BitTorrent client to implement such a system through the distributed hash table (DHT) method. An alternative and incompatible DHT system, known as Mainline DHT, was developed simultaneously and later adopted by the BitTorrent (Mainline), μTorrent, Transmission, rTorrent, KTorrent, BitComet, and Deluge clients.

Current versions of the official BitTorrent client, μTorrent, BitComet, Transmission and BitSpirit all share compatibility with Mainline DHT. Both DHT implementations are based on Kademlia. As of version 3.0.5.0, Vuze also supports Mainline DHT in addition to its own distributed database through use of an optional application plugin MainlineDHT Plugin. This potentially allows the Vuze client to reach a bigger swarm.

Most BitTorrent clients also use Peer exchange (PeX) to gather peers in addition to trackers and DHT. Peer exchange checks with known peers to see if they know of any other peers. With the 3.0.5.0 release of Vuze, all major BitTorrent clients now have compatible peer exchange.

IPv6 support[edit]

One of the options for this HTTP based tracker protocol is the "compact" flag. This flag, as defined in BEP 23,[3] specifies that the tracker can compact the response by encoding IPv4 addresses as a set of 4 bytes (32 bits). IPv6 addresses, though, are 128 bits long, and as such, the "compact" would break IPv6 support. To handle that situation clients and trackers must either avoid using compact announces over IPv6 or implement BEP 07[4]

Software[edit]

opentracker from Dirk Engling powered one of the biggest BitTorrent trackers, The Pirate Bay tracker.

qBittorrent is an open source BitTorrent client with a built-in tracker support.

BitTorious is an open source, commercially supported tracker with integrated web-based management portal.

See also[edit]

References[edit]

  1. ^ Di, Wu; Dhungel, Prithula; Hei, Xiaojun; Zhang, Chao; Ross, Keith. "Understanding Peer Exchange in BitTorrent Systems - New York University" (PDF). Retrieved 22 December 2022.
  • ^ Jones, Ben (15 January 2008). "Trading BitTorrent Tracker Invites, Commodity or Curse?". TorrentFreak. Archived from the original on 19 June 2013. Retrieved 23 October 2010.
  • ^ Harrison, David. "Tracker Returns Compact Peer Lists". Archived from the original on 2010-02-11. Retrieved 2017-02-28.
  • ^ Hazel, Greg; Norberg. "IPv6 Tracker Extension". Archived from the original on 2017-05-15. Retrieved 2017-02-28.

  • Retrieved from "https://en.wikipedia.org/w/index.php?title=BitTorrent_tracker&oldid=1219881151"

    Categories: 
    BitTorrent tracker
    Application layer protocols
    BitTorrent
    Servers (computing)
    Hidden categories: 
    Articles with short description
    Short description is different from Wikidata
    Articles needing additional references from March 2009
    All articles needing additional references
    Wikipedia articles that are too technical from August 2012
    All articles that are too technical
    Articles with multiple maintenance issues
     



    This page was last edited on 20 April 2024, at 12:12 (UTC).

    Text is available under the Creative Commons Attribution-ShareAlike License 4.0; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.



    Privacy policy

    About Wikipedia

    Disclaimers

    Contact Wikipedia

    Code of Conduct

    Developers

    Statistics

    Cookie statement

    Mobile view



    Wikimedia Foundation
    Powered by MediaWiki