Seeker2

Possibly related to: [Massive duplicate announces by libtorrent clients](https://github.com/arvidn/libtorrent/issues/6551) ...or part of the causes of that anyway.

> 10gig dual stack seedboxes running qbittorrent would often have 4 announces due to them having both a 10g and 1g nic, even though the tracker itself doesn't have an...

This might be easier to resolve if libtorrent didn't report [different peerIDs on each interface](https://github.com/qbittorrent/qBittorrent/issues/19391) it uses and even [different from the ones it sends to trackers](https://github.com/arvidn/libtorrent/issues/7479).

There's multiple kinds of priority a seeding torrent could be given. What's talked about here is mostly torrent-level priority. But if 1 super-busy seeding torrent has 50+ peers and all...

Speedtest your internet connection with nothing else going on. You may not have much upload bandwidth and that's where most of the overloads are occurring. qBitTorrent's settings file might be...

All the more reason to post your qBitTorrent settings or try extremely low advanced settings values for stuff like outgoing connections per second and Max concurrent HTTP announces. Another thing...

Especially since this occurs: https://github.com/qbittorrent/qBittorrent/issues/14844

The seeds retrying seeds problem is far worse than first appears, if using uTP: https://github.com/arvidn/libtorrent/issues/3542#issuecomment-1257038658 It can flood out other connections for seeds... ...even appearing to cause massive file losses...

> In my test I have two peers, one seed and one downloader. After the transfer is complete neither peer is attempting to connect to the other. In my case,...

> > even appearing to cause massive file losses and/or hard drive damage for other BitTorrent > > Then this a bug either in hardware, or firmware of HDD or...