You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Torrents that rely exclusively on the DHT are not a problem, except that Brave is currently not persisting the DHT table to disk between instantiations of the WebTorrent client (i.e. new WebTorrent()) This means that the DHT bootstrap nodes must be contacted each time the WebTorrent client is re-created, as the previous table entries are discarded when the client is destroyed (which happens where there are no more active torrent tabs).
The bootstrap nodes typically refuse to respond to clients who repeatedly contact them, as their intended purpose is to bootstrap new clients into the network by returning some ip:ports of other clients in the network, after which the bootstrap node should never need to be contacted again (unless all ip:ports that a client is aware of have gone offline).
Long story short, if the bootstrap nodes refuse to reply, then a torrent that has no working tracker servers will just refuse to start downloading because no peers can be found.
Start and stop the torrent download repeatedly (say 5 times)
After this, start the torrent and note that it will refuse to start downloading
If it is working, then it's possible that the tracker server has come back online. Confirm that contacting the tracker server (http://bttracker.debian.org:6969/announce) fails by checking chrome://inspect/#extensions for a network error to this URL.
Actual result:
Torrent with no working tracker server fails to download after repeatedly started and stopped.
Expected result:
Torrent with no working tracker server should download with no issues after repeatedly started and stopped.
Description
Certain torrents rely exclusively on the DHT to find peers, and have no functioning tracker servers. Here's an example torrent (https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/debian-10.0.0-amd64-DVD-1.iso.torrent). It has a single tracker server (http://bttracker.debian.org:6969/announce) that seems to be offline.
Torrents that rely exclusively on the DHT are not a problem, except that Brave is currently not persisting the DHT table to disk between instantiations of the WebTorrent client (i.e.
new WebTorrent()
) This means that the DHT bootstrap nodes must be contacted each time the WebTorrent client is re-created, as the previous table entries are discarded when the client is destroyed (which happens where there are no more active torrent tabs).The bootstrap nodes typically refuse to respond to clients who repeatedly contact them, as their intended purpose is to bootstrap new clients into the network by returning some ip:ports of other clients in the network, after which the bootstrap node should never need to be contacted again (unless all ip:ports that a client is aware of have gone offline).
Long story short, if the bootstrap nodes refuse to reply, then a torrent that has no working tracker servers will just refuse to start downloading because no peers can be found.
Steps to Reproduce
chrome://inspect/#extensions
for a network error to this URL.Actual result:
Torrent with no working tracker server fails to download after repeatedly started and stopped.
Expected result:
Torrent with no working tracker server should download with no issues after repeatedly started and stopped.
Reproduces how often:
Intermittent issue
Brave version (brave://version info)
All versions.
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: