projects:ipv6-bittorrent
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
projects:ipv6-bittorrent [2010/01/03 00:52] – created berni | projects:ipv6-bittorrent [2015/04/19 20:40] (aktuell) – berni | ||
---|---|---|---|
Zeile 3: | Zeile 3: | ||
=== IPv6? === | === IPv6? === | ||
- | [[http:// | + | [[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:// | ||
=== IPv6 and Bittorrent === | === IPv6 and Bittorrent === | ||
- | Most Bittorrent clients, including [[http:// | + | Most Bittorrent clients, including [[http:// |
- | In general BitTorrent clients have three ways to aquire lists of possible endpoints. | + | Unfortunately, |
== Tracker == | == Tracker == | ||
Zeile 18: | 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:// | 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:// | ||
- | While the software side was easy IPv6-support never got much traction in public trackers. Aside from projects like the [[http:// | + | Clients supporting this are µTorrent and Vuze, as well as all libtorrent (Rasterbar) based clients. The major exception is Transmission, |
+ | |||
+ | While the software side was easy IPv6-support never got much traction in public trackers. Aside from projects like the [[http:// | ||
+ | |||
+ | |||
+ | == Peer Exchange == | ||
+ | |||
+ | With Peer Exchange (or PEX) clients that are connected to each other can share information about the third-party clients connected to them. This is implemented in all major clients. | ||
+ | |||
+ | |||
+ | == Distributed Hash Table == | ||
+ | |||
+ | With Distributed Hash Tables (DHT) clients can build a self-maintaining overlay network between each other (Peer-to-Peer) and exchange any kind of information over it. In Bittorrent this is used to find the connection information for peers sharing the same content. For IPv4 DHT is supported for all major clients. | ||
+ | |||
+ | Azureus/ | ||
+ | |||
+ | An official standard for IPv6 DHT has recently been standardized in [[http:// | ||
+ | |||
+ | The most widely used client µTorrent does not support any kind of IPv6 DHT yet. | ||
+ | |||
+ | |||
+ | == Conclusion == | ||
+ | |||
+ | IPv6 could play a much larger role in BitTorrent today if the trackers would be available over IPv6 as well. PEX does not work too well with the current density of IPv6 peers, and DHT is either completely unsupported (µTorrent) or will not be upgraded to in large numbers within the next 12 months (Transmission 1.80+). | ||
+ | |||
+ | |||
+ | === The Project === | ||
+ | |||
+ | In order to aid BitTorrent over IPv6 for the [[http:// | ||
+ | |||
+ | This tracker is free for use by all **legal** Bittorrent content. I do not have time nor energy to fight with the owners of illegally shared content. Please respect my wishes and do not use this tracker for questionable content. If this happens nevertheless I might be forced to limit the tracker to known content (by hash). If you have legal content you want to share using this tracker please consider sending me the hash, I will add it to the whitelist. | ||
+ | |||
+ | |||
+ | == How to use == | ||
+ | |||
+ | The announce URL (used at torrent creation) is [[http:// | ||
+ | |||
+ | **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:// | ||
+ | |||
+ | == mktorrent == | ||
+ | |||
+ | This section is about [[http:// | ||
+ | |||
+ | $ mktorrent -a < | ||
+ | |||
+ | == mktorrent-borg == | ||
+ | |||
+ | There is also [[http:// | ||
+ | |||
+ | $ mktorrent -a < | ||
+ | |||
+ | == Azureus/ | ||
+ | |||
+ | When you create a new torrent, put your IPv4 tracker into the Announce URL on the first page and check the " | ||
+ | |||
+ | == µ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/ | ||
+ | |||
+ | The old python reference implementation [[http:// | ||
+ | |||
+ | $ btmakemetafile < | ||
+ | |||
+ | you can also use the included tool btreannounce with the same parameters to change an already existing .torrent file. | ||
+ | |||
+ | |||
+ | == Statistics == | ||
+ | |||
+ | This is still a TODO item. Various experimental graphs can be found [[http:// | ||
+ | |||
+ | |||
+ | === Current Users === | ||
+ | |||
+ | Projects currently using this tracker include | ||
+ | |||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | |||
+ | ==== Contact ==== | ||
+ | |||
+ | If you have further questions or comments don't hesitate to contact me. | ||
+ | |||
+ | E-Mail: [[berni+tracker@birkenwald.de]] | ||
+ | |||
+ | IRC: berniv6 @freenode or @IRCnet | ||
projects/ipv6-bittorrent.1262479957.txt.gz · Zuletzt geändert: 2015/04/19 20:06 (Externe Bearbeitung)