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
Sender
qBittorrent: 4.6.7 x64
Operating system: Windows Server 2022 Datacenter 21H2 20348.2527
Qt: 6.4.3
libtorrent-rasterbar: 1.2.19.0
What is the problem?
When the packet loss of μTP, it will not actively use BT, resulting in 0 speed
When two qbit clients connect, using the default options, there will be a momentary connection to μTP (UDP), and then the connection will be lost due to network environment reasons
The option μTP-TCP mixed mode algorithm (mixed_mode_algorithmqbit) = Perfer TCP does not actively use BT (TCP)
If TCP is turned off in the settings(Peer connection protocol = TCP), It can be successfully connected and the speed can reach the upper limit of broadband
qBittorrent & operating system versions
qBittorrent: 5.0.2 x64
Operating system: Windows 11 23H2 22631.4460
Qt: 6.7.3
libtorrent-rasterbar: 1.2.19.0
qBittorrent: 4.6.7 x64
Operating system: Windows Server 2022 Datacenter 21H2 20348.2527
Qt: 6.4.3
libtorrent-rasterbar: 1.2.19.0
What is the problem?
When the packet loss of μTP, it will not actively use BT, resulting in 0 speed
When two qbit clients connect, using the default options, there will be a momentary connection to μTP (UDP), and then the connection will be lost due to network environment reasons
The option
μTP-TCP mixed mode algorithm (mixed_mode_algorithmqbit)
=Perfer TCP
does not actively use BT (TCP)If TCP is turned off in the settings(
Peer connection protocol
=TCP
), It can be successfully connected and the speed can reach the upper limit of broadbandSteps to reproduce
μTP-TCP mixed mode algorithm (mixed_mode_algorithmqbit)
=Perfer TCP
Peer connection protocol
=TCP and μTP
Sender: Seeding
Receiver: Downloading (For connection stability, add peer: Sender's [IPv6]:port)
Additional context
No response
Log(s) & preferences file(s)
qBittorrent.ini.txt
The text was updated successfully, but these errors were encountered: