- cross-posted to:
- piracy@lemmy.ml
- cross-posted to:
- piracy@lemmy.ml
cross-posted from: https://lemmy.ml/post/6915117
The release of qBittorrent v4.6.0 stable comes with I2P support. While experimental, we can still get a working torrent setup using qBittorrent now. qBittorrent-nox is the Web-UI only version, and currently it does not have configuration settings in the Web-UI for I2P settings. This guide will show you how to setup qBittorrent-nox and manually change the
qBittorrent.conffile to allow for I2P torrenting!Guide can be found here: https://strict3443.codeberg.page/i2p-info/hugo/public/posts/how-to-use-i2p-on-qbittorrent-nox/
qBittorrent Changelog: https://github.com/qbittorrent/qBittorrent/blob/release-4.6.0/Changelog
You must log in or # to comment.
Running I2P on my pc just in case :)
The I2P network thanks you.
Does anyone know if it’s possible to setup I2P on a local server and then point to that, when setting up the proxy settings in Firefox from your PC?
Yes, absolutely. I have a VPS that runs a i2pd router and I can set my clients to point to my VPS and I am able to use the I2P network. In doing so, I had to make sure I forwarded the correct ports on my VPS so that it would reach the i2pd application. I will do a write up soon.
Thanks, that sounds awesome. This would also allow me to run I2P 24/7, helping the network, instead of having my PC run all the time.
Here is an ansible role you can use to deploy i2pd to linux servers and such: https://codeberg.org/systemfailure.net/ansible_i2pd. Otherwise, on most distros the i2pd package should be able to be installed from the package managers in the terminal.
It should be perfectly doable. The only difference is that the server in on the local network (e.g. 192.168.1.101) instead of localhost (127.0.0.1). You might need to configure your OS firewall to let traffic through.
What are the advantages of doing so and how does it differ from vanilla setup?
What @supervent@lemmy.dbzer0.com said. Basically you get access to the I2P network (overlay on top of the regular internet) that provides anonymity and doesn’t require any port forwarding. Thus, this allows every user to seed torrents without worrying about opening ports or getting letters in the mail.
The torrent space on I2P is still growing, there are some chads cross-seeding to the I2P network allowing for torrenting popular torrents over I2P.
No need of a VPN or pay anything to protect yourself.
If you can find the torrents you want on I2P, it’s sadly alot smaller then clearnet for torrents currently
That is the lacking area. There needs to be a development in the area of DHT crawlers and indexers to help find torrents on I2P like how btdigg works, but for I2P torrents. Hopefully one day.
Question: Can I keep it connected to some VPN layer like
gluetun, and still make I2P work? Ideally, it should route all the clearnet traffic throughgluetunand the I2P traffic throughi2pd.From the instructions, it looks like it should be possible, just confirming.
Yes, I did exactly this when I2P support was first in beta. I have a docker stack with Gluetun as my network for all my *arr containers and I was able to still point my qBittorrent to my i2pd router and it worked just fine.
