qBittorrent WebUI: i2p configuration

IngwiePhoenix commented 10 months ago

Suggestion

Hello!

I worked my way from Reddit posts, to Lemmy reposts, into this issue tracker and then pull requests and finally found the used i2p options: https://github.com/Vort/qBittorrent/blob/1910cbf57b4108f68cb75ddd46ea756df5a482a9/src/base/bittorrent/sessionimpl.cpp#L527-L534C57 Whilst this is part of a PR, I believe it was merged, so those options should be correct.

However, it doesn't seem like these options are yet configurable in the WebUI (qbittorrent-nox, if I am not mistaken?).

I mainly use qBittorrent with the linuxserver.io container together with Gluetun and an additional firewall rule so QB can even reach my non-docker i2pd. So, chances are that I am missing something.

Anyway; short and simple: Configurable I2P options in the WebUI. Related settings in qBittorrent.conf:

[BitTorrent]
Session\I2P\Address=192.168.2.1
Session\I2P\Port=7656
Session\I2P\Enabled=true
Session\I2P\MixedMode=true
Session\I2P\InboundQuantity=3
Session\I2P\OutboundQuantity=3
Session\I2P\InboundLength=3
Session\I2P\OutboundLength=3

Use case

Deploying qBittorrent as part of a software suite also means having to use the WebUI (or an alternative version of it). So having the options in the settings panel there would be much appreciated!

Extra info/examples/attachments

None I can think of, honestly. Though I likely oversaw something... in which case, I apologize. :)

luzpaz commented 10 months ago

@PriitUring can we close ticket ?

IngwiePhoenix commented 10 months ago

Good morning!

Apologies; I added the thumbs-up while traveling and spent the weekend sleeping out a cold, so I did not have the time to write a proper reply.

I intend to wait for 4.6.1 to be released and then see how fast the devs at linuxserver.io will respond to updating to the new version. For the meantime, I pieced myself a configuration together and even got to confirming it with a torrent of I2PSnark. Whilst it took a significant amount of time for the initializing, it eventually connected and downloaded.

This, however, led me to looking at the Proxy settings. I looked at them this morning again to remember why it stuck to my mind, because I went to sleep shortly after that. In there, it says that it can use a proxy for BitTorrent purposes and peer resolution. Are any of those settings required? Since the trackers also live in the i2p network, I would assume that I would need to tell QP to connect to those trackers using i2p as well. Do you possibly have some info there? Haven't tried anything in this section yet, though.

Thanks for your replies and sorry again for going silent. I do feel much better and recovered now though. :)

LuposX commented 2 months ago

@IngwiePhoenix is it nowadays possible to configure the qBittorent WebUi with the I2P options? Thought, I asked here before I try the docker container from linuxserver.

IngwiePhoenix commented 2 months ago

@LuposX It should be; but I honestly haven't verified. Spin up a temporary container, you can even take away its network by setting the network driver to none. Pop the webui and check. But, if I am not mistaken, this change should have landed. However, since I am not sure, I have not closed this issue yet.

LuposX commented 2 months ago

I tried it, I keep getting the error: "Waiting for i2p acceptor from SAM bridge", I found this link tutorial i2p where someone in the comment says this happens because "libtorrent" needs to have a higher version then 2.0, but I checked the package list and libtorrent version of the docker package is greater than 2.0. So I am not sure what the problem ist.

qbittorrent / qBittorrent