I'm trying to move over from transmission on my laptop to qbittorrent on my NAS. I have it running rootlessly in a podman container. I wanted the stats to show up on my heimdall webUI so I put both containers into the same network with a Network=heimdallnet line in their quadlets and fired them up again. It worked, except DHTs are dead and the qbittorrent stays firewalled.

After spending too much time on this issue, I asked chatgpt for advice. It suggested I do an iptables rule to allow for nat from the bridge network to the outside world. That did resolve the firewall status but DHTs stayed dead. I gave up and removed the Network=heimdallnet line.

I'm sure this is doable, but I'm not quite smart enough to understand what I did wrong.

Any opinions on how the two compare?

I disabled UPnP for security reasons and want to port forward qBittorrent.

Lets say the port I chose is 8999, do I need to port forward 8999 TCP and 8999 UDP? Or can I just port forward 8999 TCP? Or can I just port forward 8999 UDP?

And WTF is uTP? There no option to port forward uTP ports in my router or VPN.

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.conf file 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

qBittorrent v4.6.0 Release

Sun Oct 22th 2023

qBittorrent v4.6.0 was released today with a lot of new features and bug fixes. Here are some of the most notable changes for end users:

Features:

• Added experimental I2P support
• Provided a UI editor for the default theme
• Made various UI theming improvements
• Implemented a torrent tags editing dialog
• Revamped the "Watched folder options" and "Automated RSS downloader" dialogs
• Allowed the use of another icons in dark mode
• Allowed adding new torrents to the queue top
• Allowed filtering the torrent list by save path
• Exposed the 'socket send/receive buffer size' options
• Exposed the 'max torrent file size' setting
• Exposed the 'bdecode limits' settings
• Added options to adjust the behavior of merging trackers to an existing torrent
• Added an option to stop seeding when a torrent has been inactive
• Allowed the use of a proxy per subsystem
• Expanded the scope of the "Proxy hostname lookup" option
• Added a short

cross-posted from: https://lemmy.ml/post/4912475

https://codeberg.org/Strict3443/qbittorrent-i2p-vnc

I have created a Dockerfile which will compile the latest version of qBittorrent which has experimental I2P support into a docker container with VNC support. The reason for this is my server is headless and I wanted to use the v4.6.x version of qBittorrent, but the qbittorrent-nox version of v4.6.x does not have I2P options yet. So I had to build the GUI version on top of a VNC image.

In doing so, this will build a container that has VNC capabilities where you can utilize a desktop environment to setup the GUI version of qBittorrent with your I2P settings, and then just use the web-ui from there on.

Why?

I am a qBittorrent user and wanted to start downloading and cross-seeding torrents with I2P, so I built this image as a drop in replacement of my linuxserver/qbittorrent docker container and it just works.

Why don't you post the docker image?

I am n