Jigen

That's cool thank you!!

Most of the issues related to i2p have been fixed in libtorrent with this commit: https://github.com/arvidn/libtorrent/commit/94ed94ec1468e786bea2610c59586c4bf2994697 I've personally tested the fixed library with deluge-torrent and apart some minor issues it...

These are the settings that [Deluge](https://github.com/deluge-torrent/deluge) exposes to the user:  which essentially enable the settings in libtorrent mentioned by @Vort (plus some extra ones).

This is a code snippet related to that (not C++ deluge is written in python): **core/preferencesmanager.py** ``` def _on_set_proxy(self, key, value): # Initialise with type none and blank hostnames. proxy_settings...

I've tried to modify some code to add i2p support but for some library problems (outdated qt5 on my system) couldn't try a build: https://github.com/qbittorrent/qBittorrent/commit/cd7b9ea701fae1d5d746c0e38868cc4552c476bf so I didn't go ahead....

As side note, since i2p is for anonimity and privacy maybe could be useful to force proxy use when in i2p mode to prevent leaking. Extra options for those that...

To try mixed mode a torrent with both i2p and clearnet seeds would be needed, and so far I hadn't the chance to test. In deluge is possible to set...

@Vort thanks, now I've corrected it

> @jiigen your commit was almost right. I fixed it a little: [585dbeb](https://github.com/qbittorrent/qBittorrent/commit/585dbebcc5ee9de246cd9ab2a20cd79679a16fea) And here are the results: So it retrieve peers and the download starts that's a good starting...

> But [client_test](http://libtorrent.org/client_test.html) shows peer list correctly! So it's something in both client we didn't find so far. I can't do reliable tests atm cuz I'm building in quickly built...