As long as the torrent stays private and has a unique infohash (which is not publicly available) there are no other peers that are outside the swarm than those known by the tracker. Azureus will return the uploaded/downloaded/remaining values to the tracker as usual. Note for private tracker communities (disabling DHT) Īzureus' distributed database won't interfere with the normal tracker-client communication since it's only a fall-back mechanism and doesn't kick in on healthy torrents unless explicit specified by the users. You shouldn't use that flag when you expect the tracker to be healthy. Note: Setting those flags usually has no huge benefit besides it guarantees that a Magnet Link to this torrent will work. torrent file (outside the info dictionary, opposing to the private flag):ġ8:azureus_propertiesd17:dht_backup_enablei1e20:dht_backup_requestedi1ee To explicitly request DHT tracking of a torrent even when its legacy tracker is up and running you can add the following dictionary entry to the. Torrent creators can explicitly prevent (even when the tracker is down) or request (instead of fallback only behavior) the use of the Distributed tracker through flags in the. But please be aware that that puts additional load on the DDB especially when you run many torrents at once, thus the developers propose not to use this option. for the ChatPlugin) to provide a mean of fast data transport for arbitrary messages through the Azureus messaging protocol for many peersĪzureus users can switch it from the fallback only to always use behavior by disabling the check-box under Tools -> Options -> Plugins -> Distributed Tracker, which will enable other peers to locate the torrent through magnet links. The downside is that currently no other Client is able to connect to those torrents
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |