-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Comments
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 |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Edit: I was wrong :) They have SOCKS outproxy support (or i2pd does at least) |
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 |
To follow this ticket. |
any update on this? |
Dear all, @arvidn has done a PR in libtorrent: Time to test this draft! |
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
The text was updated successfully, but these errors were encountered: