I2P Only Mode (depends on upstream libtorrent)

qbittorrent / qBittorrent

qBittorrent BitTorrent client

https://www.qbittorrent.org

Other

28.51k stars 4k forks source link

I2P Only Mode (depends on upstream libtorrent) #19913

Open OvercookedBeef opened 1 year ago

OvercookedBeef commented 1 year ago

Suggestion

qBittorrent added I2P support in 4.6.0, but it currently only uses I2P for torrents with I2P trackers. My suggestion is a mode that uses I2P for every torrent. I2P has outproxy support so it won't just fail on a regular torrent.

Use case

I2P only mode would ensure that no traffic went outside of I2P. This means that people without a VPN can add torrents without worry of leaking, similar to qBittorrent's network interface option.

Extra info/examples/attachments

No response

Techwolf commented 1 year ago

I use I2PSnark and have added many torrent that have no i2p tracker and they work just fine due to DHT. So an I2P only mode will work on all torrents.

OvercookedBeef commented 1 year ago

I use I2PSnark and have added many torrent that have no i2p tracker and they work just fine due to DHT. So an I2P only mode will work on all torrents.

libtorrent doesn't support DHT for I2P https://github.com/arvidn/libtorrent/issues/7408

OvercookedBeef commented 1 year ago

Are you sure this depends on upstream? Does libtorrent not have a way to force a torrent to use I2P? This feature request doesn't depend on DHT, DHT can just be disabled for now when I2P only is on.

OvercookedBeef commented 11 months ago

Depends on https://github.com/arvidn/libtorrent/issues/7461

OvercookedBeef commented 9 months ago

~Turns out that I2P only has HTTP(S) outproxy support, and not SOCKS. This feature request is still useful for~

~Non-I2P HTTP(S) trackers: You might think that Non-I2P trackers wouldn't have I2P peers, but maybe they serve their tracker both over clear web and I2P, but the torrent only has the clear web tracker added to it~
~Preventing leaks: This is an important one, as I had previously added a torrent, expecting it to be over I2P, but it wasn't. The magnet had net=I2P in it, but it appears qBittorrent/libtorrent doesn't support this (other clients like BiglyBT do, from looking at their source code)~

Edit: I was wrong :) They have SOCKS outproxy support (or i2pd does at least)

OvercookedBeef commented 4 months ago

I believe the old issue I linked may not be enough for I2P only mode, so I've made a specific issue about it: https://github.com/arvidn/libtorrent/issues/7716 React to it with a :+1: to show support for it.

Neustradamus commented 2 days ago

To follow this ticket.