You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update: qBittorrent 4.6.2 AppImage on Linux (libtorrent 2.0.9.0) allows one host to download multiple torrents despite setting allow_multiple_connections_per_ip being disabled (unticked) and qBittorrent restarted. So if this is not a bug, it may be per torrent connection limit. Setting is described as a peers related, so likely it does not apply on trackers or any other connections, so i am unsure why the setting is marked as "It is not recommended to enable this feature."
The text was updated successfully, but these errors were encountered:
@slrslr allow multiple connections per ip is not a limit, it's a switch to enable connecting to peers with the same IP address (but different ports). It's off by default because it's an effective countermeasure against certain kind of abuse.
It can not be set per torrent, because you can't know which torrent an incoming connection belongs to until after accepting it and handshaking.
But, it sounds like you might really be looking for the connection limits instead.
Please provide the following information
libtorrent version (or branch): 2.0.9.0
platform/architecture: Debian
compiler and compiler version: ?
https://www.libtorrent.org/reference-Settings.html#allow_multiple_connections_per_ip does not mention if it is global or per torrent connection limit. If global, then can you please also allow per torrent limit? That should be set to 1 connection possibly.
Update: qBittorrent 4.6.2 AppImage on Linux (libtorrent 2.0.9.0) allows one host to download multiple torrents despite setting allow_multiple_connections_per_ip being disabled (unticked) and qBittorrent restarted. So if this is not a bug, it may be per torrent connection limit. Setting is described as a peers related, so likely it does not apply on trackers or any other connections, so i am unsure why the setting is marked as "It is not recommended to enable this feature."
The text was updated successfully, but these errors were encountered: