D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: irotjaf on October 10, 2010, 06:10:47 PM
-
Hi all,
The problem is simple. When I download torrents the NAS eats up all internet bandwidth. I use to limit the bandwidth but why to keep torrents forever limited if I use internet only half of the day.
So, anybody have a solution to keep torrents uploading/downloading with maximum speed by prioritizing home computers over NAS?
I read somewhere that a solution could be a router with QoS (quality of service) implementation which knows that a certain local IP (e.g. NAS) has the lowest priority compared to the other local IPs. Does anybody use this? Is this correct? Would it be useful to keep torrent traffic maximized without affecting internet?
At the moment I cannot even hear an internet radio without interruptions when I set unlimited speed to torrents. I have a router which may have QoS but putting that in the network involves a completely different configuration from my actual one (Modem -> Gigabit Switch -> Wifi point)
-
check you modem settings, it might have QoS...
If not, try and just limit the upload speed of your Torrents to about 60% of your max theorical speed
like if you have a connection that can upload at max 1Mbps (125KB/s), set it at 600Kbps (100KB/s)
this should let you d/l at max speed while not interrupting the rest of your web activities
But best would be a QoS that would prioritise, either by IP or by protocol used...
-
Thank you.
-
I agree with Buhric. Use the QoS settings in your router if available. This should allow you to maximize your bandwidth without throttling all the time, or constantly having to tweak the torrent speeds.
Regards,
Wiggs
-
I installed fun_plug and then transmission BT client. Transmission has a feature that lets you schedule throttling of DL/UL speed at some specific hours. Works like a charm.
-
My intent was to maximize internet traffic at any time, no matter at what time I wake up or go to sleep. If the connection is there why not to use it in maximum, even for seeding torrents. This should be done automatically, computers have to think for me.
Now, one question still remains to me. Have anybody had experience with QoS and torrents? Does it work well? Does it understand for example that I am uploading a video to youtube and need 95% of bandwidth and leave the rest to keep torrent connections alive? Or does it suck all the bandwidth toward my youtube upload and make the torrents die for the moment. I've never used QoS, so it's a bit hard to understand what is going to be and how the router will understand how much bandwidth my computer needs without killing completely NAS connectivity to the internet.
I appreciate any description you can give from your personal experience.
-
I use a Tomato firmware on a WRT54GL (switched from DD-WRT). I use QoS rules based on IP address since I set the DNS-323 with a static IP. It works very well for me. There are methods that are based on deep packet inspection, but are much more complicated (CPU intensive) and less than 100% accurate (that depends on the type of traffic/protocol you're trying to control). That's why I used IP-based rules.
To the best of my knowledge this type of traffic shaping makes sense if you want to control your upload bandwidth usage. It's not effective to do it on your downloads.
-
One of the problems with torrents of unlimited bandwidth is that most of traffic goes for uploads and downloads start to suffer. This has been my experience too, when I remove the upload limit. For this reason, people recommend to set upload limit to half of the total bandwidth.
Anybody has dealt with this side of the problem too. Do you remove the upload limit when using QoS?
-
Well this is "normal" behaviour
Even when you are downloading only, you are still sending information back to the source
like acknowledging that you received the packet that was send, requesting another packet, etc...
so if you are using all your available upload bandwith to actualy upload data, theres none left for the download "control" part... thus your downloading starts to suffer....
So its always good practice to limit your upload bandwith when dealing with p2p, limit it at around 60-70%of your theorical maximum...
And yes if you are using QoS, you can select which protocol has priority, but like scaramanga said, this is very CPU intensive, and is not always 100% accurate.
Best options for you are to QoS by IP or by Port if you can...
Since we are talking about the DNS, QoS by IP would probably be better.... just assing the DNS-323 IP the lowest priority possible... So whenever a different IP (computer) is doing something it will have priority over the DNS-323.
This way, QoS will give all the bandwith that the other IP requires, and leave the rest to the DNS-323.