If I were to change this port (as in title) number manually to foil ISP blocking/shaping, would I have to manually set up a corresponding router port forwarding rule? The use upnp/nat-pmp option is set to true. Or do I only need to manually set a router port forwarding rule if the upnp option is unticked?
Other questions:
- what does the anonymous mode do?
- are the torrent queuing options good for fine tuning uploads?
Port used for incoming connections
-
- Administrator
- Posts: 2443
- Joined: Sun Jan 23, 2011 1:17 pm
Re: Port used for incoming connections
[quote="qbituser"]
If I were to change this port (as in title) number manually to foil ISP blocking/shaping, would I have to manually set up a corresponding router port forwarding rule? The use upnp/nat-pmp option is set to true. Or do I only need to manually set a router port forwarding rule if the upnp option is unticked?[/quote]
upnp/natmpm does that for you. Check the log to see if it worked(View->Execution Log). Manual portforwarding is needed when upnp/natpmp is disabled or when your router doesn't support upnp/natpmp
[quote="qbituser"]Other questions:
- what does the anonymous mode do? [/quote]
If you clicked on "More information" which is next to the "enable anomymous mode" option you would go to this page: https://github.com/qbittorrent/qBittorr ... ymous-Mode
If you don't what you are doing don't enable it. You'll probably suffer performance issues.
[quote="qbituser"]
- are the torrent queuing options good for fine tuning uploads?
[/quote]
What do you mean by "fine tuning uploads"? The available options are in Tools->Options...->BitTorrent->Torrent Queueing
If I were to change this port (as in title) number manually to foil ISP blocking/shaping, would I have to manually set up a corresponding router port forwarding rule? The use upnp/nat-pmp option is set to true. Or do I only need to manually set a router port forwarding rule if the upnp option is unticked?[/quote]
upnp/natmpm does that for you. Check the log to see if it worked(View->Execution Log). Manual portforwarding is needed when upnp/natpmp is disabled or when your router doesn't support upnp/natpmp
[quote="qbituser"]Other questions:
- what does the anonymous mode do? [/quote]
If you clicked on "More information" which is next to the "enable anomymous mode" option you would go to this page: https://github.com/qbittorrent/qBittorr ... ymous-Mode
If you don't what you are doing don't enable it. You'll probably suffer performance issues.
[quote="qbituser"]
- are the torrent queuing options good for fine tuning uploads?
[/quote]
What do you mean by "fine tuning uploads"? The available options are in Tools->Options...->BitTorrent->Torrent Queueing
Re: Port used for incoming connections
Thanks.
I changed the port number and the ul speed was slow so I thought npnp wasn't working but it was just a coincidental that I wasn't getting much requests at that particular time. upnp is working ok after the port number change.
Now, if I changed the listening port number to 6882 or some other port number (under the 'Connection' options), would I also have to change the port number under the 'Use a different port number for DHT and bittorrent' under the 'BitTorrent' options?
The default torrent queuing options is disabled by default. What are the default hardcoded values used by bittorrent? I'm assuming that torrent queuing is in operation although the toggle option is unticked by default. I'm assuming that it is possible to tweak (using the queuing options) to allow only a certain number of uploads say 2, which would mean ul speed of 100kbps for each ul slot if the max ul speed is set to 200kbps.
I changed the port number and the ul speed was slow so I thought npnp wasn't working but it was just a coincidental that I wasn't getting much requests at that particular time. upnp is working ok after the port number change.
Now, if I changed the listening port number to 6882 or some other port number (under the 'Connection' options), would I also have to change the port number under the 'Use a different port number for DHT and bittorrent' under the 'BitTorrent' options?
The default torrent queuing options is disabled by default. What are the default hardcoded values used by bittorrent? I'm assuming that torrent queuing is in operation although the toggle option is unticked by default. I'm assuming that it is possible to tweak (using the queuing options) to allow only a certain number of uploads say 2, which would mean ul speed of 100kbps for each ul slot if the max ul speed is set to 200kbps.
Re: Port used for incoming connections
Did you have it enabled to use a different port? If not, you can leave it.
I don't think there is any default bittorrent hardcoded values. Your question about queuing is a bit more complicated than just saying 2 uploads at once so they must split their upload speed evenly. It's more or less supply and demand, if only one torrent has traffic it will use the whole upload speed. If your intention was to be sure a single torrent doesn't exceed a set limit you would have to use per torrent upload rate. (In addition to global upload rate) Say for example you have global rate set to 200, then you have a particular popular torrent but you also want to be sure it doesn't use the entire bandwidth, set it to 100 on that torrent. That way you're assured at least 100 for other torrent, or up to 200 if the set one is not uploading. However if you set both of them with per torrent bandwidth limit and only one is currently uploading you are basically wasting half your upload capacity.
I don't think there is any default bittorrent hardcoded values. Your question about queuing is a bit more complicated than just saying 2 uploads at once so they must split their upload speed evenly. It's more or less supply and demand, if only one torrent has traffic it will use the whole upload speed. If your intention was to be sure a single torrent doesn't exceed a set limit you would have to use per torrent upload rate. (In addition to global upload rate) Say for example you have global rate set to 200, then you have a particular popular torrent but you also want to be sure it doesn't use the entire bandwidth, set it to 100 on that torrent. That way you're assured at least 100 for other torrent, or up to 200 if the set one is not uploading. However if you set both of them with per torrent bandwidth limit and only one is currently uploading you are basically wasting half your upload capacity.
Re: Port used for incoming connections
Thats what I'm asking. I've already changed the port number under 'Listening port'-'Port used..." option.
So what you are saying is that the torrent queuing mechanism is not in effect if the option is left unticked?
So what you are saying is that the torrent queuing mechanism is not in effect if the option is left unticked?
-
- Administrator
- Posts: 2443
- Joined: Sun Jan 23, 2011 1:17 pm
Re: Port used for incoming connections
I am not sure but the defaults are: The default values are 8 active downloads and 5 active seeds. link->http://www.rasterbar.com/products/libto ... ml#queuing
You can test it yourself though.
About the DHT port: I cannot find it in the libtorrent docs but I think in the libtorrent 0.16.x series you cannot specify a separate port for DHT, so this option doesn't have some use. I could be wrong though.
EDIT: Different DHT port is deprecated API in libtorrent 0.16.x and will be removed in the next series. However it can be still be used in the 0.16.x series. The new behavior will be "use same port as the bittorrent protocol".
You can test it yourself though.
About the DHT port: I cannot find it in the libtorrent docs but I think in the libtorrent 0.16.x series you cannot specify a separate port for DHT, so this option doesn't have some use. I could be wrong though.
EDIT: Different DHT port is deprecated API in libtorrent 0.16.x and will be removed in the next series. However it can be still be used in the 0.16.x series. The new behavior will be "use same port as the bittorrent protocol".
Last edited by sledgehammer_999 on Wed May 01, 2013 10:05 pm, edited 1 time in total.
Re: Port used for incoming connections
Thanks you've answered all my queries succinctly and more.
So it looks like the DHT port option may be a superfluous do-nothing thingy, thats probably why it didn't seem to work like it should in my router testing.
So it looks like the DHT port option may be a superfluous do-nothing thingy, thats probably why it didn't seem to work like it should in my router testing.