starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Clearnet peers Overpower and Dethrone I2P peers in Mixed Mode settings #16542

New issue

Open

opened 2026-02-22 03:12:28 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-22 03:12:28 -05:00

Owner

Originally created by @absolutep on GitHub (Jan 13, 2025).

qBittorrent & operating system versions

Qt: 6.8.0
Libtorrent: 2.0.10.0
Boost: 1.86.0
OpenSSL: 3.4.0
zlib: 1.3.1
qBittorrent v5.1.0beta1 (64-bit)
Windows 10

What is the problem?

Whenever in a Mixed Mode torrent - if both the kind of peers are present they dethrone I2P peers.

Even though, I2P peers had more transfer speed than the Clearnet peers.

Once, dethroned, the I2P peers slowly fades away until their speed reaches to Zero.

After some time they get back up but do not recover proper speeds until the Clearnet peers goes away.

Image 1 = Clearnet peers enter and then not only slows down I2P peers but never lets them recover their speed until and unless Clearnet peers leaves the torrent swarm.

Image 2 = Slow I2P speed due to Clearnet peer

Steps to reproduce

download cross-seeded torrent [public+i2p]
uploading starts after completing download.
I2P peers going about their transfer
suddenly Clearnet peers enters
slows down all i2p peers and gets into top spot
i2p peers all go away,
i2p peers again enter the torrent swarm but their speeds are significantly less than what was before.
this state exists until the Clearnet peers goes away.

Additional context

Ideally, What should happen?

Both I2P & Clearnet peers should be getting seeded/leeched at their topmost speed as possible - because both of them should work separately, as in how separate tunnels work

I2P speed goes into I2P torrent speed
Clearnet speed goes into Clearnet torrent speed.

This does not happen, instead Clearnet completely overpowers and dethrones I2P peers and after sometime when Clearnet peers is finished with their transfer the I2P peers rise back to their glory.

Log(s) & preferences file(s)

13-01-2025 10:33 AM - UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP[]: no router found"
13-01-2025 10:33 AM - UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP[]: no router found"
13-01-2025 10:31 AM - Detected external IP. IP: ""
13-01-2025 10:31 AM - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Wed Jan 1 07:52:30 2025.
13-01-2025 10:31 AM - Successfully listening on IP. IP: "::1". Port: "UTP/"
13-01-2025 10:31 AM - Successfully listening on IP. IP: "::1". Port: "TCP/"
13-01-2025 10:31 AM - Successfully listening on IP. IP: "fe80::3-:44b1%8". Port: "UTP/"
13-01-2025 10:31 AM - Successfully listening on IP. IP: "fe80::3-:44b1%8". Port: "TCP/"
13-01-2025 10:31 AM - Successfully listening on IP. IP: "127.0.0.1". Port: "UTP/"
13-01-2025 10:31 AM - Successfully listening on IP. IP: "127.0.0.1". Port: "TCP/"
13-01-2025 10:31 AM - Successfully listening on IP. IP: "". Port: "UTP/"
13-01-2025 10:31 AM - Successfully listening on IP. IP: "". Port: "TCP/"
13-01-2025 10:31 AM - UPnP/NAT-PMP support: ON
13-01-2025 10:31 AM - Encryption support: ON
13-01-2025 10:31 AM - Anonymous mode: OFF
13-01-2025 10:31 AM - Peer Exchange (PeX) support: ON
13-01-2025 10:31 AM - Local Peer Discovery support: ON
13-01-2025 10:31 AM - Distributed Hash Table (DHT) support: ON
13-01-2025 10:31 AM - HTTP User-Agent: "qBittorrent/5.1.0beta1"
13-01-2025 10:31 AM - Peer ID: "-qB5100-"
13-01-2025 10:31 AM - Trying to listen on the following list of IP addresses: "0.0.0.0:,[::]:"
13-01-2025 10:31 AM - Using config directory: C:\Users\AppData\Roaming\qBittorrent
13-01-2025 10:31 AM - qBittorrent v5.1.0beta1 started. Process ID: 3968

Originally created by @absolutep on GitHub (Jan 13, 2025). ### qBittorrent & operating system versions Qt: 6.8.0 Libtorrent: 2.0.10.0 Boost: 1.86.0 OpenSSL: 3.4.0 zlib: 1.3.1 qBittorrent v5.1.0beta1 (64-bit) Windows 10 ### What is the problem? Whenever in a Mixed Mode torrent - if both the kind of peers are present they dethrone I2P peers. Even though, I2P peers had more transfer speed than the Clearnet peers. Once, dethroned, the I2P peers slowly fades away until their speed reaches to Zero. After some time they get back up but do not recover proper speeds until the Clearnet peers goes away. **Image 1 = Clearnet peers enter and then not only slows down I2P peers but never lets them recover their speed until and unless Clearnet peers leaves the torrent swarm.** ![2](https://github.com/user-attachments/assets/acf425ca-5209-4363-a80f-d0e651bd672d) **Image 2 = Slow I2P speed due to Clearnet peer** ![3](https://github.com/user-attachments/assets/6a3ed2d5-21e7-4882-9c75-e95acb4cee95) ### Steps to reproduce 1. download cross-seeded torrent [public+i2p] 2. uploading starts after completing download. 3. I2P peers going about their transfer 4. suddenly Clearnet peers enters 5. slows down all i2p peers and gets into top spot 6. i2p peers all go away, 7. i2p peers again enter the torrent swarm but their speeds are significantly less than what was before. 8. this state exists until the Clearnet peers goes away. ### Additional context **Ideally, What should happen?** Both I2P & Clearnet peers should be getting seeded/leeched at their topmost speed as possible - because both of them should work separately, as in how separate tunnels work I2P speed goes into I2P torrent speed Clearnet speed goes into Clearnet torrent speed. This does not happen, instead Clearnet completely overpowers and dethrones I2P peers and after sometime when Clearnet peers is finished with their transfer the I2P peers rise back to their glory. ### Log(s) & preferences file(s) 13-01-2025 10:33 AM - UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP[]: no router found" 13-01-2025 10:33 AM - UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP[]: no router found" 13-01-2025 10:31 AM - Detected external IP. IP: "" 13-01-2025 10:31 AM - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Wed Jan 1 07:52:30 2025. 13-01-2025 10:31 AM - Successfully listening on IP. IP: "::1". Port: "UTP/" 13-01-2025 10:31 AM - Successfully listening on IP. IP: "::1". Port: "TCP/" 13-01-2025 10:31 AM - Successfully listening on IP. IP: "fe80::3-:44b1%8". Port: "UTP/" 13-01-2025 10:31 AM - Successfully listening on IP. IP: "fe80::3-:44b1%8". Port: "TCP/" 13-01-2025 10:31 AM - Successfully listening on IP. IP: "127.0.0.1". Port: "UTP/" 13-01-2025 10:31 AM - Successfully listening on IP. IP: "127.0.0.1". Port: "TCP/" 13-01-2025 10:31 AM - Successfully listening on IP. IP: "". Port: "UTP/" 13-01-2025 10:31 AM - Successfully listening on IP. IP: "". Port: "TCP/" 13-01-2025 10:31 AM - UPnP/NAT-PMP support: ON 13-01-2025 10:31 AM - Encryption support: ON 13-01-2025 10:31 AM - Anonymous mode: OFF 13-01-2025 10:31 AM - Peer Exchange (PeX) support: ON 13-01-2025 10:31 AM - Local Peer Discovery support: ON 13-01-2025 10:31 AM - Distributed Hash Table (DHT) support: ON 13-01-2025 10:31 AM - HTTP User-Agent: "qBittorrent/5.1.0beta1" 13-01-2025 10:31 AM - Peer ID: "-qB5100-" 13-01-2025 10:31 AM - Trying to listen on the following list of IP addresses: "0.0.0.0:,[::]:" 13-01-2025 10:31 AM - Using config directory: C:\Users\AppData\Roaming\qBittorrent 13-01-2025 10:31 AM - qBittorrent v5.1.0beta1 started. Process ID: 3968

deekerman added the

Libtorrent

I2P

labels

2026-02-22 03:12:28 -05:00

deekerman commented

2026-02-22 03:12:33 -05:00

Author

Owner

@thalieht commented on GitHub (Jan 13, 2025):

Libtorrent is probably responsible for this.

@thalieht commented on GitHub (Jan 13, 2025): Libtorrent is probably responsible for this.

deekerman commented

2026-02-22 03:12:38 -05:00

Author

Owner

@absolutep commented on GitHub (Jan 13, 2025):

Upstream libtorrent issue added = https://github.com/arvidn/libtorrent/issues/7812

@absolutep commented on GitHub (Jan 13, 2025): Upstream libtorrent issue added = https://github.com/arvidn/libtorrent/issues/7812

deekerman commented

2026-02-22 03:12:40 -05:00

Author

Owner

@Neustradamus commented on GitHub (Jan 30, 2025):

@zzzi2p: What do you think about this ticket?

Linked to:

https://github.com/arvidn/libtorrent/issues/7812

@Neustradamus commented on GitHub (Jan 30, 2025): @zzzi2p: What do you think about this ticket? Linked to: - https://github.com/arvidn/libtorrent/issues/7812