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.
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.
I've never looked at the source code of a PT, but my understanding is that they also implement heuristics to detect strange behaviors, i.e. clients trying to fake their ratio.
Not all of them do, but yes. Since it is the client who send all the info (bytes sent/received, version, etc), anything can be spoofed.
The tracker, having access to the stats of all the client on a specific torrent can find "unusual" client (for example, a client that report a lot of bytes sent while no other client report downloading/receiving anything, or the opposite). But due do quirks of the networks, delay and possible lost stats messages, they still have to be pretty permissive of small discrepancies. Also, all use an ID in the tracker url for each client to discriminate them and associate them with their account on the website. And some are not very careful about the ID generation algorithm, leading to being easily able to find other account peer ID, and so you can use them to download to preserve your ratio. I even found at least one private tracker that did not care if you passed a non-existent peer ID.
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
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.
They usually ban VPNs for website use but allow them for seedboxes (sometimes requiring approval). The rationale is to stop account sharing and ban evasion.
It's really not. Even if they aren't recruiting new members you can buy an account or invites. You could also prepare alternate accounts ahead of time.
> 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.
If you spoof the client name and your client ends up misbehaving/misreporting you'll just get banned for cheating.
It's harder to ban people if you allow using VPNs.
It's really not. Even if they aren't recruiting new members you can buy an account or invites. You could also prepare alternate accounts ahead of time.