Comments on: Multi-tracker Problems http://www.bemasher.net/archives/683?utm_source=rss&utm_medium=rss&utm_campaign=multi-tracker-problems Code, Computers, Photography and Guns Sun, 01 Jan 2012 23:13:16 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Shawn Russ http://www.bemasher.net/archives/683/comment-page-1#comment-534 Shawn Russ Sat, 31 Jul 2010 06:55:49 +0000 http://www.bemasher.net/?p=683#comment-534 ok so put a space between each one... cool cuase I use utorrent thank you. ok so put a space between each one… cool cuase I use utorrent thank you.

]]> By: bemasher http://www.bemasher.net/archives/683/comment-page-1#comment-533 bemasher Sat, 31 Jul 2010 06:53:36 +0000 http://www.bemasher.net/?p=683#comment-533 The order in which the trackers appear doesn't matter. However you must have an extra line between each tracker in order for μtorrent to parse them properly. I'm not sure if this is a problem for other bittorrent clients. The order in which the trackers appear doesn’t matter. However you must have an extra line between each tracker in order for μtorrent to parse them properly. I’m not sure if this is a problem for other bittorrent clients.

]]> By: Shawn Russ http://www.bemasher.net/archives/683/comment-page-1#comment-532 Shawn Russ Sat, 31 Jul 2010 06:50:35 +0000 http://www.bemasher.net/?p=683#comment-532 Hey so I have always wondered about what you two are talking about for years I'm talking, so anyways it leave off unclear to me, is it best to put a space between the udp and http trackers of the same name or do I group them together? Any help would be much appreciated, thanx. Hey so I have always wondered about what you two are talking about for years I’m talking, so anyways it leave off unclear to me, is it best to put a space between the udp and http trackers of the same name or do I group them together? Any help would be much appreciated, thanx.

]]> By: bemasher http://www.bemasher.net/archives/683/comment-page-1#comment-378 bemasher Tue, 02 Feb 2010 00:35:20 +0000 http://www.bemasher.net/?p=683#comment-378 Hmm, now that I think about it you are right. If a torrent lists multiple trackers and lets say that one of them isn't parsed out properly, none of the clients will see it and it's not an issue because nobody is looking at it, there will be no orphaned peers assuming that they are able to connect to at least one of the other trackers anyway. And in this case openbittorrent is the same tracker operating through different protocols, same applies to publicbt as well. Still I find it annoying that people don't bother to check that when they add trackers that they will parse out properly anyway. Hmm, now that I think about it you are right. If a torrent lists multiple trackers and lets say that one of them isn’t parsed out properly, none of the clients will see it and it’s not an issue because nobody is looking at it, there will be no orphaned peers assuming that they are able to connect to at least one of the other trackers anyway. And in this case openbittorrent is the same tracker operating through different protocols, same applies to publicbt as well.

Still I find it annoying that people don’t bother to check that when they add trackers that they will parse out properly anyway.

]]> By: JJJ http://www.bemasher.net/archives/683/comment-page-1#comment-376 JJJ Thu, 28 Jan 2010 21:16:10 +0000 http://www.bemasher.net/?p=683#comment-376 The first example you posted is actually correct, I think, the second example is considered "abusive". Each group of trackers without a space between them is a group. µTorrent tries to connect to one random tracker of each group. If the tracker doesn't work, µTorrent tries another tracker of that group. Multiple groups are handled simultaneously. The reason for this, is that the trackers grouped together share peer data. You only need to connect to one of them, because they both have the same peer data. For example: http://track-01.rarbg.com:8080/announce http://track-02.rarbg.com:8080/announce http://track-03.rarbg.com:8080/announce They're basically the same tracker, but spread across multiple servers/connections to handle the load/traffic. Now I'm not exactly sure which trackers share peer data, but that's how µTorrent works, and I'm pretty sure that trackers using similar domain names share peer data. Actually, if I'm not mistaken, http://tracker.openbittorrent.com/announce is exactly the same tracker as udp://tracker.openbittorrent.com:80/announce. Only, you're connecting to it via UDP and on port 80 with the latter address. Same with http://tracker.publicbt.com:80/announce and udp://tracker.publicbt.com:80/announce. So in this situation, the first example you posted makes sense, the second is redundant. The first example you posted is actually correct, I think, the second example is considered “abusive”.

Each group of trackers without a space between them is a group.

µTorrent tries to connect to one random tracker of each group. If the tracker doesn’t work, µTorrent tries another tracker of that group. Multiple groups are handled simultaneously.

The reason for this, is that the trackers grouped together share peer data. You only need to connect to one of them, because they both have the same peer data.
For example:

http://track-01.rarbg.com:8080/announce
http://track-02.rarbg.com:8080/announce
http://track-03.rarbg.com:8080/announce

They’re basically the same tracker, but spread across multiple servers/connections to handle the load/traffic.

Now I’m not exactly sure which trackers share peer data, but that’s how µTorrent works, and I’m pretty sure that trackers using similar domain names share peer data.

Actually, if I’m not mistaken, http://tracker.openbittorrent.com/announce is exactly the same tracker as udp://tracker.openbittorrent.com:80/announce. Only, you’re connecting to it via UDP and on port 80 with the latter address. Same with http://tracker.publicbt.com:80/announce and udp://tracker.publicbt.com:80/announce. So in this situation, the first example you posted makes sense, the second is redundant.

]]>