Difference between revisions of "Libtorrent"

From I2P Wiki
Jump to navigation Jump to search
m (fix wording)
m (fix not showing client_test link)
Line 7: Line 7:
 
== Issues ==
 
== Issues ==
   
Currently (early 2023), the peer count shows the right numbers, but the peer list (both in libtorrent's client_test<ref name="client_test">[https://github.com/arvidn/libtorrent/blob/RC_2_0/examples/client_test.cpp] - a basic full implementation of libtorrent</ref> and qBittorrent) shows only one peer with an IP address of "0.0.0.0:0".<br />
+
Currently (early 2023), the peer count shows the right numbers, but the peer list (both in libtorrent's client_test<ref name="client_test">https://github.com/arvidn/libtorrent/blob/RC_2_0/examples/client_test.cpp - a basic full implementation of libtorrent</ref> and qBittorrent) shows only one peer with an IP address of "0.0.0.0:0".<br />
 
(client_test shows multiple 0.0.0.0's, while qBittorrent shows only one.)
 
(client_test shows multiple 0.0.0.0's, while qBittorrent shows only one.)
   
Line 13: Line 13:
   
 
== libtorrent ==
 
== libtorrent ==
For libtorrent's client_test<ref name="client_test" /> program, the following command can be used to leech/seed a magnet<ref>This example shows I2P+'s 2.1.0 Windows installer</ref> through I2P (by [https://github.com/arvidn/libtorrent/issues/7262#issuecomment-1383848366 Vort]):
+
For libtorrent's client_test<ref name="client_test" /> program, the following command can be used to leech/seed a magnet<ref>This example uses I2P+'s 2.1.0 Universal Installer.</ref> through I2P (by [https://github.com/arvidn/libtorrent/issues/7262#issuecomment-1383848366 Vort]):
   
 
<pre>examples/client_test --enable_dht=false --proxy_type=i2p_proxy --i2p_hostname=127.0.0.1 --i2p_port=7656 'magnet:?xt=urn:btih:889401025a1c16bbf9d8001ae157679507a87feb&dn=I2P%2B+Universal+Installer+2.1.0%2B&tr=http://tracker2.postman.i2p/announce.php'</pre>
 
<pre>examples/client_test --enable_dht=false --proxy_type=i2p_proxy --i2p_hostname=127.0.0.1 --i2p_port=7656 'magnet:?xt=urn:btih:889401025a1c16bbf9d8001ae157679507a87feb&dn=I2P%2B+Universal+Installer+2.1.0%2B&tr=http://tracker2.postman.i2p/announce.php'</pre>

Revision as of 01:22, 27 January 2023

libtorrent-rasterbar is a BitTorrent library written in C++. It is used by popular clients, such as qBittorrent (Qt) and Deluge (Python).

I2P Support

The I2P support is available through the SAMv3 bridge in libtorrent. It was broken until late 2022 after a thread on zzz.i2p[1], resulting in several patches being merged upstream[2][3].

Issues

Currently (early 2023), the peer count shows the right numbers, but the peer list (both in libtorrent's client_test[4] and qBittorrent) shows only one peer with an IP address of "0.0.0.0:0".
(client_test shows multiple 0.0.0.0's, while qBittorrent shows only one.)

Examples

libtorrent

For libtorrent's client_test[4] program, the following command can be used to leech/seed a magnet[5] through I2P (by Vort):

examples/client_test --enable_dht=false --proxy_type=i2p_proxy --i2p_hostname=127.0.0.1 --i2p_port=7656 'magnet:?xt=urn:btih:889401025a1c16bbf9d8001ae157679507a87feb&dn=I2P%2B+Universal+Installer+2.1.0%2B&tr=http://tracker2.postman.i2p/announce.php'

You can press 'h' within client_test to see the available options.

qBittorrent

For qBittorrent, until the I2P support is added[6], one needs to build using Jiigen's fork:

git clone https://github.com/jiigen/qbittorrent -b i2p-support jiigen_qbit
cd jiigen_qbit
mkdir build
cd build
cmake ..
make
sudo make install

And within the Settings->Connection->Proxy, one needs to set "Proxy Type" to I2P, the host/port to SAM bridge's host/port, and needs to tick "proxy for peer connections/host lookups".

(Note: One might also want to enable Anonymous Mode. (Settings->BitTorrent->Enable anon.mode))

References

External links