summer

@arvidn was this a duplicate of https://github.com/arvidn/libtorrent/issues/6772 or they're different issues?

Are all these announce requests or there are scrape requests as well? I think in queued state qbit will periodically scrape the tracker to get latest seed/leech stats. Also have...

How do you know that user isn’t using a script to announce more often? Have you tried reaching one of them?

Does your tracker resolve to both IPv6 and IPv4? Does the client claiming about duplicate counts have multiple IP addresses? Also why do you treat started and other events differently?...

>I don't. Different ip and two different peers should explain the double counting. > You should be using something else other than the IP address to treat peers uniquely. Such...

That’s why you have to add userid to it to make a combined unique hash.

If someone decided to listen on random port in qbt, then each interface gets a unique port from system. So if they’re announcing from multiple IP, your tracker will detect...

It’s a good idea for privacy and if the user doesn’t care about incoming connections.

I had a discussion with arvidn before regarding different ports for each interface when using random ports https://github.com/arvidn/libtorrent/issues/5746

A working fix is underway people! (currently for windows only) https://github.com/qbittorrent/qBittorrent/pull/16485