torreting thru socks5

Anyone use qbittorrent thru socks proxy? I tried dante and shadowsocks-libev. Shadowsocks is slow af, dante is very tricky and flexible, but I'm not sure I'm doing it right. Qbittorrent itself is very tricky and flexible as well. I kinda managed to configure something, it did work well for download (peaking at like 12mb/s), but something seems wrong with uploads: they are rare, and never fast. My config: logoutput: syslog internal: eth0 port = 1080 external: eth0 method: username client pass { from: 0.0.0.0/0 to: 0.0.0.0/0 log: connect error } socks pass { from: 0.0.0.0/0 to: 0.0.0.0/0 command: bind connect udpassociate log: error connect method: username } socks pass { from: 0.0.0.0/0 to: 0.0.0.0/0 command: bindreply udpreply log: error connect } I also tried to turn off dht+peer exchange+local peer discovery in qbt, and it immediately started uploading few torrents, with extremely fuarrrking low speeds, and then it stopped... wtf. Nah,there's nothing of value about this on the internets. And yes, I have nice speeds in general, expecting to see like 7-15mb/s peaks for uploads.

seeding is hard if you don't have open ports, since most people don't have open ports either, and so it's a catch-22, nobody can make the first move. upnp, which would tell your router "open this port temporarily for me please", can't tell the proxy the same thing. if you wanted to accept inbound connections, you'd need a separate reverse proxy, as far as i know you can't be the "server" over socks5. a seedbox sounds like what you really need

and how many days did you wait to determine that nobody downloads anything and that the speed is terrible? and what did you download such that you can reasonably expect it to be downloaded every day?

>>89181 I want it to go like this: seeds <-> vps socks server <-> my pc I don't understand why my vps can't just open soykaf ton udp connections with peers on arbitrary ephemeral ports and multiplex them all together into a single socks connection with me. Bandwidth is more than enough. What's so technically problematic about this? Maybe it's dante being bad at udp or something? Maybe qbittorrent is inherently bad at socks? >>89182 To be fair, I didn't wait enough to be sure, need to wait more. I wonder if anyone has good experience with torrenting over socks or even shadowsocks. And by good I mean at least few Tb per month outgoing traffic. I've had more than 10 Tb with the same VPS over wireguard last month, but when it got slightly broken I noticed I enjoy not having global VPN connection and rather prefer to have clearnet + local tor/i2p over clearnet + socks. With global VPN it's significantly harder to route anything else over clearnet. And I have no clue how to pull a non-global VPN trick - wg-quick doesn't seem to support this scenario well. Otherwise I could just make a side wg connection for torrents only.

Holy fuarrrking soykaf, I'd never expect something so obscure and convoluted like this, and coming from ChatGPT added to that, to work, but it fuarrrking did, from the first try. Guess I can just run qbt in vps-ns now.

>>89185 > I can just run qbt in vps-ns now Turns out, this was the hard part... sudo -E ip netns exec vps-ns runuser -u lain -- flatpak run org.qbittorrent.qBittorrent And also this to visudo: lain ALL=(ALL) NOPASSWD:SETENV: /usr/bin/ip netns exec vps-ns * Deer lord, I've been sitting on this for hours.