Arvid Norberg
Arvid Norberg
Yes, libtorrent use the SAM protocol. The main problem with libtorrent's i2p support is that it does not have any regression tests, so it's possible that it has broken at...
there must be more alerts than that, right? things like announces to the trackers for instance.
oh, you're probably setting the mask after everything already happened. set the mask as part of the ``settings_pack`` and pass that into the session constructor
yeah, it seems like there's an issue with the i2p support in the http_connection or http_tracker_connection. The proper fix for this includes implementing a simple mock SAM server in the...
this error message: "*** tracker error: (161) Waiting for i2p acceptor from SAM bridge" suggests that the SAM connection isn't being established correctly. That's no excuse to assert or crash...
does this help any? https://github.com/arvidn/libtorrent/pull/2564
@reichKV do you think you will have a chance to try that patch?
there's a bit of a chicken and egg-problem. i2p has definitely worked. Last time I looked at it I made some fixes and got it to work. The problem is...
it seems this thread is drifting a bit off-topic. libtorrent (used to) support i2p via its SAM bridge (which on the libtorrent side is configured as a kind of proxy)....
option (1) shouldn't be too difficult. I imagine you could have a job run on all torrent completions that defrag the files for that torrent. e.g. `sudo e4defrag `.