Majibow

Established Members
  • Content Count

    32
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Majibow

  • Rank
    Advanced Member
  1. All in the title but I'll explain. Not every torrent but quite a few especially if there are a small number of peers <10, but it has happened on very popular ones too 2000+ peers, get stuck after downloading the initial piece, I have been observing this bug for a number of years actually and many different pcs, but it just crossed my mind to report it now. Basically, you'll start downloading a torrent or magnet and it will just get stuck on the first piece, if you click on the pieces tab you see the piece is complete but the torrent is jammed until you press stop and then start and then it resumes at full speed. This happens with the following windows disk cache settings: [X] Override automatic cache size.... [<any value say 1024>] [ ] Reduce memory usage when cache not needed [X] Enable caching of disk writes --[ ] Write out untouched blocks every two minutes [ ] Write out finished blocks immediately [X] Enable caching of disk reads [ ] Turn off read caching if slow [ ] Remove old blocks from cache [X] Increase cache size when thrashing If you check the box for "Write out untouched blocks every two minutes" torrents will resume instantly instead of using start stop, in fact if that box is checked this issue never occurs (I have never noticed it) but without it, it happens quite frequently that a torrent will be stuck indefinitely and never progress until you intervene with a stop and start.
  2. The stateful IPv6 firewall running on a router blocks inbound connections in the very same way as IPv4 NAT. There is a solution to this and that is to support "WANIPv6FirewallControl" call (UPnP IGD v2). uTorrent currently supports UPnP for IPv4 where both port forwarding and firewall rules are created on the router but does not make a request for IPv6 firewall on the router and hence is blocked to unsolicited inbound IPv6 traffic. There is a related thread here on the Transmission client forums https://forum.transmissionbt.com/viewtopic.php?t=19275. I will also add that miniupnpd daemon can be compiled with support to receive these requests as this is the daemon that runs on a lot of SOHO routers. IPv6 is not exposed to the internet as you may initially think, which is why this is required. The user would need to manually disable IPv6 firewall as it is usually on by default (undesirable). The key thing to remember when implementing this is that, when IPv6 is configured as slaac with privacy extensions enabled the Temporary address will change every few hours... therefore uTorrent will need to either periodically refresh the pin-holing or I think the better solution is to use the permanent address for UPnP Pin-holing and reporting to torrent trackers while the temporary address should be used for outbound connections to other clients.