-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make smart ban optional #22076
Comments
Hmm, turns out the smart ban plugin is not the only mechanism for banning peers. |
#15193 being a clear example of why this wouldn't hurt |
@mirh It has nothing to do with that. Besides, the issue with archive.org torrents is solely an issue with archive.org itself, and has nothing to do with qBittorrent. |
I mean, my log showed:
|
Yeah, that looks to be it. Although, as I already said above
So automatic bans can't be disabled completely on qBittorrent side. |
Btw, this message is wrong actually. Your error has absolutely nothing to do with DNS. qBittorrent/src/base/bittorrent/sessionimpl.cpp Lines 5968 to 5970 in 6fe0289
It assumes that all possible web seed errors could be from DNS lookup only. Which is simply not true as we can see. The message probably should be replaced by something neutral, like |
Suggestion
Currently, qBittorrent enables libtorrent's smart ban plugin unconditionally. It automatically bans peers sending corrupted pieces.
qBittorrent/src/base/bittorrent/sessionimpl.cpp
Line 1698 in 7487cd7
So maybe it is a good idea to make it optional. A simple checkbox in advanced settings would suffice, I think.
Use case
Some users claim that there are use cases when it is undesirable behavior.
Like downloading a rare torrent with only 1 seed with unstable connection. Any traffic overhead in such situation is justified.
Extra info/examples/attachments
No response
The text was updated successfully, but these errors were encountered: