qBittorrent

132 readers

1 users here now

Everything related to the qBittorrent

https://www.qbittorrent.org/

https://www.qbittorrent.org/donate

founded 2 years ago

MODERATORS

mr_MADAFAKA@lemmy.ml

DHT dies in podman? (lemm.ee)

submitted 2 weeks ago by muusemuuse@lemm.ee to c/qbittorrent@lemmy.ml

3 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] brickfrog@lemmy.dbzer0.com 1 points 2 weeks ago* (last edited 2 weeks ago)

Status is firewalled and theres no DHT

When you select the torrent in qBittorrent and click the Trackers tab does DHT display "working" ?

Status is firewalled and theres no DHT but the download works and there are no errors in the log.

I suspect you had it partially correct with your earlier test. One thing is that DHT works via UDP (from what I understand) while non-DHT torrents can be TCP or UDP. So I sort of suspect that you kind of had it half working with the iptables rule earlier but you only had it working for TCP, hence only TCP torrents get through which means no DHT and uTP torrenting.

So your solution is one/both of

Re-configure your iptables rule to allow both TCP and UDP if it wasn't already
Play around with podman to get it to also publish the UDP port(s), not just TCP. According to this site podman only publishes TCP by default, there's some extra syntax for --publish to specify the protocol. Maybe you need to give it multiple publish flags so you can use both TCP and UDP on the same port(s), not too sure on that.

https://ittavern.com/notes/podman-publish-udp-port-to-host/

I looked at an i2p torrent I was playing with too and its showing the trackers are non responsive now, but theres no error in the logs.

I2P is a very different configuration, best not to compare that to regular clearnet torrenting. qBittorrent doesn't suport DHT over I2P so you'll never see DHT working in that configuration.