![]() Once you start connecting to them (per the list supplied by your tracker) then you are effectively poking very specific holes in your firewall for communication to happen to (and from) very specific places. Most home router firewalls (with UPNP disabled) will automatically block incoming connections as well which creates this same problem of peers not being able to connect to you. Whenever your software gets an updated list of peers and contacts new peers then you will get new data flowing outwards as well as inwards. The VPN is probably doing exactly what you expect, blocking unknown host connections, but once you contact someone through it you have effectively established a two way pipe between you and a peer. You may be blocking inbound requests from unknown hosts, but by contacting a peer and requesting data from it yourself you are initiating a two way data connection that they can use to not only send data, but to request it as well. Prhaps the most common issue is that clients typically don’t re-check the Tracker for updates except at 20 min intervals or so, so even if you are up and registered with the Tracker, it may be another 20 minutes or so before a specific peer will get the info your new node exists.The peers don't need to know your real IP, you are giving them a way to contact you by simply contacting them yourself.Įven if the tracker shares an unreachable IP (your VPN) and other peers fail to connect, directly at least, you make yourself reachable by contacting those peers yourself. If your machine appear brand new and especially without anything to offer you often start at the bottom of the list of priorities. There are an unlimited number of possible causes for slow starts ranging from recognizable networking issues to simply how the application “works.” Today’s torrent clients commonly apply weights on availability, reliability and more. Disk subsystems are in another universe of speed compared to networking. Placing on an SSD will not improve performance. Same with DHT, both perform similar functions, allowing each Peer to perform as a mini-Tracker so if the main Tracker is unreachable the peers by themselves can exchange enough info to start exchanging. Peer exchange help, but how effective depends on a lot of vagaries. Otherwise… I shall boot Windows, erase Linux, and sayīad things about it to all my friends. How come not on Linux!? Solve my problem. ![]() This is understandable, with obnoxious brats giving what could be seenĪs ultimatums on various forums, which boils down to: ![]() Other machine retains 11.4 for the moment, as I don’t use it much. Speeds are far below the HDD’s speed limit, but an SSD has a way smaller One thing that intrigues me: if I move the completed files to an SSDĭrive, would it affect seeding performance anyhow? Of course, the upload One thing I did is to open a UDP port in suseĪnd router’s firewalls. I’m not too familiar with DHT and how to get it properly started and LIke your above remark that means about: “I can use Torrent on another OS (Windows), including seeding (which imho proves that router, ISP, etc, allow it), but on openSUSE …” A more technical description on what can be done on another OS, so that LInux users can understand what it is in general IT terms would be then be more informative. But there are sometimes people here that simply say things like: “what is the Linux equivalent of this and this on Windows”. Well, I don’t care how well/bad Windows does as such, because I freed myself from it since quite some time (except to occasionnally do very unproductive stuff). I guess you see this as an attempt to benchmark and compare the merits of the two OSes. I meant to say: “I observed different results on another OS, while under the same network, router, ISP, etc.”, which I believe to be useful information to rule out hardware issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |