Hello.
I have qBittorrent running on Windows on my desktop and on Linux on my laptop. I have some torrents seeding on my laptop and I wanted to copy them on my desktop. I decided to copy the magnet links to my desktop qBittorrent and seed them from my laptop to my desktop just out of curiosity. My internet speed caps at 11MB/s, but my LAN router is gigabit and it should sustain much more than that easily. After figuring out the firewall settings for my laptop I got one torrent to download with 20MB/s from my laptop to my desktop (+some extra from external peers), which was great.
But after that, the rest of the torrents started at maybe 5-6MB/s downloading from my laptop then it slowed down. Looking on the peer list from my desktop I see that my laptop is not sending any data and the connection to it is marked as snubbed. If I ban all the other peers the connection works again. What can cause this? Is the laptop client not offering any data and the desktop client not asking for data so the connections just sits there idle (unless there are no other peers and the desktop client is forced to ask for data)?
Both computers are running qBittorrent v4.1.1 without speed limits and 500 connections limit per torrent.
Local peer gets snubbed
Re: Local peer gets snubbed
1.Are you getting hash fails from it?
2.Have you tried disabling uTP?
3.Why 500 connections per torrent?! Over 100 is nuts for your connection even if you're only running 1 torrent.
2.Have you tried disabling uTP?
3.Why 500 connections per torrent?! Over 100 is nuts for your connection even if you're only running 1 torrent.
Re: Local peer gets snubbed
@Switeck
1. No, no hash failures.
2. No.
3. My bad, it's actually 500 global maximum number of connections. Can this cause issues?
1. No, no hash failures.
2. No.
3. My bad, it's actually 500 global maximum number of connections. Can this cause issues?
Re: Local peer gets snubbed
500 ip connections would hose most wifi links, but hardwired 1 gbit/sec Ethernet cables should be fine with that.
Try disabling uTP and retesting. I've seen a couple problems with uTP, especially over LAN. Hard to measure latency for uTP speed control when even cpu/HDD load changes are greater than the latency floor of a good 1 gbit/sec Ethernet LAN.
Try disabling uTP and retesting. I've seen a couple problems with uTP, especially over LAN. Hard to measure latency for uTP speed control when even cpu/HDD load changes are greater than the latency floor of a good 1 gbit/sec Ethernet LAN.