Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- projects:ipv6-bittorrent [2010/01/03 01:31] – berni
+++ projects:ipv6-bittorrent [2015/04/19 20:40] (aktuell) – berni
@@ Zeile 3: / Zeile 3: @@
 === IPv6? ===
-[[http://en.wikipedia.org/wiki/IPv6|IPv6]] is the successor of the currently common communication protocol used in the Internet, IPv4. It is currently mainly used by power users, but should gain traction among endusers pretty soon.
+[[wp>IPv6]] is the successor of the currently common communication protocol used in the Internet, IPv4. It is currently mainly used by power users, but should gain traction among endusers pretty soon. By restoring end-to-end connectivity (without NAT) it is especially helpful for P2P-applications like BitTorrent.
 If you do not have IPv6 connectivity and want to experiment with it you can get free tunneled connectivity from various providers, including [[http://www.tunnelbroker.net|HE]] and [[http://www.sixxs.net|SixXS]].
@@ Zeile 10: / Zeile 10: @@
 === IPv6 and Bittorrent ===
-Most Bittorrent clients, including [[http://www.utorrent.com|µTorrent]], [[http://azureus.sf.net|Azureus]] and [[http://www.transmissionbt.com|Transmission]] support exchanging data with both IPv4 and IPv6 peers at the same time today. Unfortunately, to exchange data with IPv6 peers they have to find them first, which has been a problem for quite a while now.
+Most Bittorrent clients, including [[http://www.utorrent.com|µTorrent]], [[http://azureus.sf.net|Azureus]], [[http://www.transmissionbt.com|Transmission]] and [[http://www.rasterbar.com/products/libtorrent/|libtorrent (Rasterbar)]] support exchanging data with both IPv4 and IPv6 peers at the same time today. [[http://libtorrent.rakshasa.no/|libtorrent (Rakshasa)]] (known for the famous rtorrent) does not support it yet, but there is a [[https://github.com/rakshasa/rtorrent/issues/59|work going on]] which will hopefully be integrated soon.
-In general BitTorrent clients have three ways to aquire lists of possible IPv6-endpoints.
+Unfortunately, to exchange data with IPv6 peers they have to find them first, which has been a problem for quite a while now. In general BitTorrent clients have three ways to aquire lists of possible IPv6-endpoints.
 == Tracker ==
@@ Zeile 20: / Zeile 20: @@
 Historically IPv6 has been supported in trackers for a long time, since the original Tracker protocol exchanged IP address information as strings and was thus agnostic of the used protocol. To reduce the overhead a compressed format for exchanging peer data has been specificed in [[http://www.bittorrent.org/beps/bep_0023.html|BEP 23]]. IPv6-extensions to this protocol are specified in [[http://bittorrent.org/beps/bep_0007.html|BEP 7]].
-Clients supporting this are µTorrent and Vuze, as well as all libtorrent (Rakshasa) based clients. The major exception is Transmission, which supports (as of Version 1.80) connecting to IPv6 peers, but not to IPv6 trackers. An explaination for this can be seen in their bugtracker (Bug#xxxx).
+Clients supporting this are µTorrent and Vuze, as well as all libtorrent (Rasterbar) based clients. The major exception is Transmission, which supports (as of version 1.80) connecting to IPv6 peers, but not to IPv6 trackers. An explaination for this can be seen in their [[http://trac.transmissionbt.com/ticket/1731|bugtracker]]. This has been somewhat fixed in version 2.20 to allow connections to IPv6-only trackers. Ubuntu has backported this change into 2.13 for Ubuntu 11.04 (Natty Narwhal).
 While the software side was easy IPv6-support never got much traction in public trackers. Aside from projects like the [[http://www.sixxs.net/tools/tracker/|SixXS IPv6 Tracker]] and [[http://www.debian.org|Debian]] the only major tracker ever gaining IPv6 support was [[http://thepiratebay.org/blog/146|The Piratebay]]. Unfortunately they suffered from outages due to overload and network problems while being in major legal disputes at the same time. Today, TPB does not run trackers anymore.
@@ Zeile 36: / Zeile 36: @@
 Azureus/Vuze has IPv6-enabled DHT since a couple of years. Unfortunately this extension is Azureus-specific, so other clients do not participate in the DHT and thus cannot be found.
-An official standard for IPv6 DHT has recently been standardized in [[http://bittorrent.org/beps/bep_0032.html|BEP 32]]. This is supported by Azureus with the additional [[http://azureus.sourceforge.net/plugin_details.php?plugin=mlDHT|mlDHT Plugin]], Transmission (starting in 1.80) and various libtorrent (Rakshasa)-based clients.
+An official standard for IPv6 DHT has recently been standardized in [[http://bittorrent.org/beps/bep_0032.html|BEP 32]]. This is supported by Azureus with the additional [[http://azureus.sourceforge.net/plugin_details.php?plugin=mlDHT|mlDHT Plugin]], Transmission (starting in 1.80) and various libtorrent (Rasterbar)-based clients.
 The most widely used client µTorrent does not support any kind of IPv6 DHT yet.
@@ Zeile 58: / Zeile 58: @@
 **ATTENTION:**
-This is an IPv6-only tracker. Clients not having IPv6 will not be able to connect. Do NOT use this as single tracker in any Torrent you create, most of the clients out there will not be able to connect. Instead, use the multi-tracker extensions as defined by [[http://bittorrent.org/beps/bep_0012.html|BEP 12]] to add several trackers to a torrent.
+This is an IPv6-only tracker. Clients not having IPv6 will not be able to connect. Do NOT use this as single tracker in any Torrent you create, most of the clients out there will not be able to connect. Instead, use the multi-tracker extensions as defined by [[http://bittorrent.org/beps/bep_0012.html|BEP 12]] to add several tracker groups to a torrent.
+== mktorrent ==
+This section is about [[http://mktorrent.sf.net|mktorrent]] by esmil, which is included in the Debian repository. There is another programm called mktorrent by borg which takes slightly different options (see below).
+  $ mktorrent -a <youripv4tracker> -a http://tracker.birkenwald.de:6969/announce -o file.torrent file
+== mktorrent-borg ==
+There is also [[http://borg.uu3.net/~borg/?mktorrent|another mktorrent implementation]] by borg.
+  $ mktorrent -a <youripv4tracker> -mt <youripv4tracker> -mt http://tracker.birkenwald.de:6969/announce -o file.torrent file
+== Azureus/Vuze ==
+When you create a new torrent, put your IPv4 tracker into the Announce URL on the first page and check the "multiple torrents" option. On the next page you need to create several tracker groups, one for each tracker you are going to add. You can do this by pressing "Edit" and adding new tracker groups using the context menu (right mouse button).
+== µTorrent ==
+When creating a new torrent put all trackers into the appropriate field, seperated by an empty line (not just a newline, an empty line). An IPv4 tracker should probably come first.
+== Bittorrent/Bittornado ==
+The old python reference implementation [[http://www.bittorrent.com/btusers/download/directory-list#section-linux|Bittorrent.com]] and its fork [[http://www.bittornado.com|Bittornado]] also support multiple trackers
+  $ btmakemetafile <youripv4tracker> --announce_list '<youripv4tracker>|http://tracker.birkenwald.de:6969/announce' file
+you can also use the included tool btreannounce with the same parameters to change an already existing .torrent file.
@@ Zeile 64: / Zeile 92: @@
 This is still a TODO item. Various experimental graphs can be found [[http://tracker.birkenwald.de/stats|here]].
+=== Current Users ===
+Projects currently using this tracker include
+  * [[http://www.knoppix.net|Knoppix]]
+  * [[http://events.ccc.de/congress/2009/wiki/Conference_Recordings|26C3 Recordings]]
+[[http://www.ubuntu.com|Ubuntu]] uses the described multi-tracker setup with their own dedicated IPv6 tracker.