Open mr-cn opened 4 years ago
Maybe your issue is similar to https://github.com/arvidn/libtorrent/issues/4412
@summerqB Issue #12665 that you closed has a network issue happening on Windows, not Linux, and it's after a network change on the client itself, regardless of the router status. In other words, possibly a duplicate, but unless @mr-cn is able to reproduce it via network changes on the client end (without router changes) and on Windows and not just Linux, then it's probably a different cause. If it is the same, then his would be a duplicate of my issue.
qBittorrent version and Operating System
4.2.5-nox on Debian 10 (OMV 5, kernel 5.5.0-0.bpo.2-amd64)
Using docker image: linuxserver/qbittorrent (the docker image uses official PPA: https://launchpad.net/~qbittorrent-team/+archive/ubuntu/qbittorrent-stable)
If on linux, libtorrent-rasterbar and Qt version
Official PPA Builds: https://launchpad.net/~qbittorrent-team/+archive/ubuntu/qbittorrent-stable
What is the problem
After router restart, the client won't reconnect the network.
All trackers are not available even when you force re-announce, and DHT nodes is 0.
The windows client will reconnect.
What is the expected behavior
Reconnect the network like how Windows client behaves.
Steps to reproduce
Extra info
I guess it's the same problem as arvidn/libtorrent#4487
And I guess it's a problem of libtorrent. If I add a torrent by link at this time, the torrent can be successfully added and just cannot start to download. The "add torrents" action should be done by qbittorrent, so qbt's network seems OK. But I am not certain so I post here.