Rejected announces from libtorrent clients proxying through SOCKS

[Frotag]

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.

[tonytamps]

The private torrent site crowd are very restrictive on which clients are allowed and even big names like qBit aren't safe enough to assume the version is allowed.

[ardanur]

You can turn a socks5 into an interface and then move it to a different namespace: https://github.com/xjasonlyu/tun2socks

[diftr]

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

[Mathnerd314]

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.

[seg_lol]

Is it because of some game theoretic information exposure? Or is this more about that you can't trust any of the VPN providers.

[orliesaurus]

why ban VPN? what about seedboxes?

[dahrkael]

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

[neko_lover]

i thought about including packet captures and some analysis on that, but ran out of steam. you're right that it would have made a more interesting post. maybe ill amend it at some point :)

there were other peculiarities i noticed in testing, like udp trackers not working through the socks proxy even after fixing the listening port problem. id like to revisit the topic at some point to see if that can be fixed as well.

[JoshGlazebrook]

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.

[ronsor]

I've genuinely never seen a server that supports the BIND command.

[immibis]

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

[neko_lover]

id be interested to know how i might get started with implementing something like that

[eptcyka]

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

[debugnik]

A quick search shows me that "annouce" is sometimes used as a noun in the context of bittorrent for some reason.