The conclusion at that time seems to be that lots of trackers lie, which screws up the websites. I think that this second issue may have been discussed a few years ago here. For example, last night when I downloaded that 7.31 GB file: the website said that there were > 200 peers, but when I started downloading it in BiglyBT, there were maybe only like 25 of them (and I was only able to connect to a few of those). Related to this is the fact that the number of peers shown in BiglyBT is often way less than what I saw on the website. That is, if there are no other incomplete peers then it is impossible to upload. Cant tell if thats because of some errors (e.g bad handsake, unknown message type 20, etc messages) or simply because Ubuntu is such a popular torrent that no peer needed anything from me. So any peers the seed has not uploaded to in 300 seconds gets automatically disconnected. peer.disconnectinactiveinterval 300 seconds (5 minutes) by default. Is what I am experiencing normal for most folks, or is there something I have misconfigured? The other upload slots upload to the first peers that come along and change peers less often. Some private trackers expect to hear the listening port announcement. Some tracker dont accept this and fail with errors such as 'Invalid Port' or 'Illegal Argument'. Since MBAM often complained when I use BiglyBT about it connecting to bad websites, I went into its "Real-Time Protection" area and turned off "Web Protection" which stopped it from complaining. Tools > Options> Connection> Transport Encryptionand uncheck Use the 'cryptoport' tracker extension to prevent plain incoming connection attempts. Before you perform the following solutions, you should check if your internet connection is stable and fast. I use both Windows Defender as well as MalwareBytes Premium (MBAM). both TCP and UDP tests immediately pass with "OK !". Often, leecher is synonymous with downloader (see above): simply describing a peer or any client that does not have 100 of the data. I use a torrent friendly VPN (Torguard), have port forwarding setup, and in BiglyBT Tools -> NAT / Firewall Test. Tools -> Options -> Connection -> Transfer: KB/s global max upload speed: 0 Tools -> Options -> Connection -> Networks: all 3 choices are checked. I have configured BiglyBT in ways that I think should allow maximum connectivity. I wish that I had captured a screenshot then. When I was downloading that big 7.3 GB torrent last night, I think that I was commonly only connecting to only 1-3 out of more like 25+ peers. The PNG file attached is the typical situation that I find myself in: I am only able to connect to a fraction of my peers:Ī) on the 7.31 GB file, I am connecting to only 1 out of 5 peers, and am only uploading a pathetic 11.2 KB / s to itī) on the 11.12 MB file, I am connecting to only 1 out of 25 peers, and am not even uploading anything to it BiglyBT Version Number 3.0.0.0, the very latest as of today.OS and version: Windows 10 for Workstations, fully patched.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |