Rejected announces from libtorrent clients proxying through SOCKS (opens in new tab)

Stuff like this is why I usually go for network namespaces + (wireguard / socks / iptables) when I need to isolate traffic.

> The tracker in question that I wanted to get this working for explicitly forbids running development builds of approved BitTorrent clients.

Also didn't realize trackers were that strict about clients. I've seen some ban buggy versions / sketchy clients (usually cloud-based or for mobile), but that's usually a for-your-own-good type thing. Major names like QBT are usually fine regardless of version.

All that and he didn't even test it with the tracker in the end? What an anticlimax.

Sounds like a very restrictive tracker... but I guess the more restrictive, the more likely it has good stuff. Seems kind of strange though because most trackers I have seen just completely ban any sort of proxy or VPN.

i was expecting a more hands on explanation of what the client sends and what the tracker responds but this post is quite abstract for a technical issue. from what i read in the PR the qBT fix is to just ignore the proxy on the listening side of things but that doesnt explain the issue

Technically you could theoretically accept incoming connections if the SOCKS5 server supports the BIND command and the client knows how to use it. It's rare though.

Since you're already using a proxy, you can have the proxy change the parameters, and then you are not modifying the client.

The headline, whilst true to the author, makes no sense. Announces is a verb, announcements is a noun.