You are not logged in.
Hi,
I've been trying qbittorrent 2.0.3 as a native KDE client. It looks and feels very lightweight and reasonable, but it doesn't seem to use all my bandwidth.
I seed a dozen torrents from open trackers, where seeders are always in short supply; my network consists of two boxes and a router. Test cases look like this:
(1) One box seeding via Transmission, another uses qbittorrent; Transmission always gets no less than 80% of the outgoing traffic.
(2) Both boxes use qbittorrent; in that case they seed on a par, but the bandwidth get underused. eth0 traffic proportionally diminished.
Where am I supposed to start my research? qbittorrent is documented rather formally, no how-tos.
PS I've been told already that I want to 'scan my ports' to determine whether they are 'open'. Unfortunately, I've absolutely no idea what the words mean. Keywords, links, suggestions are extremely welcome
Offline
On the open ports issue just make sure you have port forwarding setup right, that's what it means.
You may want to check the configs of both qbittorrent and Transmission and compare them, maybe its just a issue of less aggressive settings in qbittorrent.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
On the open ports issue just make sure you have port forwarding setup right, that's what it means.
You may want to check the configs of both qbittorrent and Transmission and compare them, maybe its just a issue of less aggressive settings in qbittorrent.
That's a lot of good advice, most certainly . Too good for me to stomach, unfortunately. Anything for dummies?
Offline
You can use http://www.canyouseeme.org/ to see if your port is open.
Offline
On the issue of the configurations, I guess comparing the values of similar or equal settings will do the trick. Maybe Transmission has better values for your connection.
The thing with torrents is that need to find the sweet spot for your connection, if you configure some things with values that are too small it will be slow, but values that are too large will make it slow too, maybe a bit of trial and error is in order
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Deleted as irrelevant.
Last edited by Llama (2010-01-01 08:56:37)
Offline
A private tracker pushed me a bit in the right direction: it quickly made me spoof uTorrent to avoid ban. It also made me change the default listening port (6881). What is so special about 6881 port? I tried Google, but nothing really enlightening turned up. Some guidelines as to how to make an informed choice of listening ports and other vital settings are welcome
Offline
You can use http://www.canyouseeme.org/ to see if your port is open.
Any port chosen at random (qbittorrent option) is reported inaccessible ("connection refused"). The whole thing works, a bit sluggishly.
Curiously, Transmission, which apparently never experienced speed troubles, also uses a closed port.
Last edited by Llama (2010-01-01 09:29:57)
Offline
Random ports are bad unless the program you use supports upnp _and_ your router supports upnp _and_ you have upnp enabled in the router.
Personally I don't like upnp, it's disabled in my router's configuration. I prefer to do manual port forwarding, this way I never get surprises. Also if you setup iptables using a random port to accept incoming connections it can be troublesome. Just choose a high port number (something in the range 49152~65535) and you should be fine.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
It looks like ports are not an issue. I've found some open ones, but it doesn't make any difference whether the listening port is use is open or closed. So the issue remains: sluggish seeding most of the time. Download speeds are always good. Ideas badly needed
Offline