Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I2P Only Mode (depends on upstream libtorrent) #19913

Open
OvercookedBeef opened this issue Nov 10, 2023 · 9 comments
Open

I2P Only Mode (depends on upstream libtorrent) #19913

OvercookedBeef opened this issue Nov 10, 2023 · 9 comments

Comments

@OvercookedBeef
Copy link

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
Copy link

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.

@luzpaz luzpaz added the I2P label Nov 19, 2023
@OvercookedBeef
Copy link
Author

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 arvidn/libtorrent#7408

@luzpaz luzpaz changed the title I2P Only Mode I2P Only Mode (depends on upstream libtorrent) Nov 19, 2023
@OvercookedBeef

This comment was marked as outdated.

@OvercookedBeef

This comment was marked as outdated.

@OvercookedBeef
Copy link
Author

OvercookedBeef commented Feb 1, 2024

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
Copy link
Author

OvercookedBeef commented Jul 27, 2024

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

@Neustradamus
Copy link

To follow this ticket.

@absolutep
Copy link

any update on this?

@Neustradamus
Copy link

Dear all, @arvidn has done a PR in libtorrent:

Time to test this draft!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants