One thing that I found strange in this IPv6-only testing was that in both qBittorrent and client_test the DHT seemed to cap out at 128 nodes. The log for the case where data was actually transferred is quite big due to the full alert mask.
test -O -enable_dht=false -enable_lsd=false -alert_mask=all ~/Downloads/ The logs were obtained with the following command lines: Or maybe it's just that the Ubuntu IPv6 tracker does not return many/useful IPv6 are the logs with client_test. In that respect, I could not reproduce your issue.īut there seems to be an issue when not using DHT.
According to your settings, you have DHT on. When DHT was off, I could not observe any activity.With both qBittorrent and client_test, I was able to connect to peers and download data only if I left DHT on.In all cases tested, this made no difference (and UPnP/NAT-PMP seemed to be working fine with my router anyway). My ISP provided router has an IPv6 port forwarding functionality.I used a standard Ubuntu 20.04 torrent, but edited to have only the IPv6 tracker in the trackers list ( ).I made sure to connect to the internet with IPv6 only.You can also use it on Linux (just change the package name to libtorrent:圆4-linux-static), but on Linux you'd probably prefer building it the "traditional" way using system tested a bit more thoroughly, here are my findings. P.S - at least on Windows, you can do vcpkg install libtorrent:圆4-windows-static as an easy way to build stuff with vcpkg. If you setup client_test with the equivalent network parameters to only use IPv6 and are successfully able to download, we'll know we'll need to take a closer look at qBittorrent's network setup code.
The point of this is to figure out whether or not this might be a problem with libtorrent or with the way qBittorrent's networking code works (including its usage of the libtorrent API).
Seems like they try to establish a connection but ultimately chance you could try client_test from When running, you can use -list-settings and -= to customize the relevant settings, and then use some tool like netstat to make sure you're using IPv6 only. The "peers"-tab occasionally shows some IPv6-peers, but they disappear after a few seconds.
0 kommentar(er)
