Arvid Norberg
Arvid Norberg
https://github.com/arvidn/libtorrent/pull/7685
libtorrent currently talks to i2p via the SAM protocol. Does this protocol support ways of contacting plain IPs and ports and speak arbitrary protocols?
It sounds like the outproxy suggestion doesn't work. Partly because there (probably) aren't enough public outproxies to support torrenting, but primarily because outproxies are for the web, not for arbitrary...
> ??? Why? It's not like clearnet DHT is being used to find I2P peers, I don't see why I2P DHT is required and why I2P trackers can't be used...
if that's an acceptable approach, there's no need to add any new features to libtorrent. You just need a tool that replaces all trackers with an i2p tracker in `.torrent`...
my guess is that there's some issue related to using "overlayfs".
from my reading, it seems you may be running a "LiveCD" installation, with the underlying operating system mounted as read-only, and then an overlayfs with a writeable partition.
I believe the `CMakeList.txt` uses glob to pick up the tests, so just removing the file would do it. When building with boost-build, you can remove the line in `tests/Jamfile`...
I think this PR would fix it. would you mind testing it on your build image? https://github.com/arvidn/libtorrent/pull/7715
the intention is to stop contacting seeds (if oneself is also a seed). I'll take a look, thanks for the report!