Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Xagest]

I'm sorry if my understanding of QoS is flawed, but I definitely need some help with this.  It has probably been answered, but none of my searches of the forum really gave me a clear answer.

So I have QoS setup in an attempt to throttle bittorrent (located on a single machine) during peak usage of the internet so that during the day, users trying to use the internet can get the best connection they can possibly get (whether it be browsing, games, or whatnot).  On off-peak usage, such as when everyone is asleep during the night or gone during the day, bittorrent should run at full speed.

However, my QoS settings don't seem to be doing squat.  This is what I have in my QoS.

Name: Bittorrent
Priority: 255
Local IP Range: 0.0.0.0 to 255.255.255.255
Remote IP Range: 0.0.0.0 to 255.255.255.255
Protocol TCP
Local Port Range: 10000 to 10000
Remote Port Range: 0 to 65535

Is there anything I'm missing here?  Do I need an "everything else" rule that has a priority of 1?  Or would QoS not help me load balance the bittorrent bandwidth at all.

[PeterJvM]

Have you setup bittorrent to use port 10000 since that's what you have set as local port range.
In my setup I have a qos rules:

1) for skype with priority 5, protocol both and the right local ports and local IP-range
2) for an internet radiostation with priority 10, protocol tcp and the right remote port and IP-nr
3) and as you for torrents with priority 255 and protocol=both(don't know why but found a link with the
    example) and the right local port and IP-nr (I use one pc thats for torrents only and it has a reserved IP-
    adres

Everything works great for me, this way.

[PeterJvM]

Here's an example where you'd use port 7000 for internet radio, port 6000 for skype and port 10000
for torrents:

--------------------------------------------------------------------

   Name         Priority                               Protocol   
   webradio    10                                     TCP

   Local IP Range                                     Local Port Range
V   192.168.4.190 to 192.168.4.199              0 to 65535

   Remote IP Range                                  Remote Port Range
   82.201.100.9 to 82.201.100.9                 8000 to 8000

--------------------------------------------------------------------

   Name         Priority                               Protocol   
   skype         5                                      Both

   Local IP Range                                     Local Port Range
V   192.168.4.190 to 192.168.4.199             6000 to 6000

   Remote IP Range                                  Remote Port Range
   0.0.0.0 to 255.255.255.255                    0 to 65535

--------------------------------------------------------------------

   Name         Priority                              Protocol   
   torrents      255                                  Both

   Local IP Range                                    Local Port Range
V   192.168.4.191 to 192.168.4.191            10000 to 10000

   Remote IP Range                                 Remote Port Range
   0.0.0.0 to 255.255.255.255                   0 to 65535
   
--------------------------------------------------------------------

[Xagest]

Not exactly what I'm asking for, though.  I want "Everything other than bittorrent" to have a higher priority than bittorrent.  Am I supposed to make a rule for every single application that needs an online connection?

[bigeyes0x0]

To achieve what you said, you need to:
- Set your client to use a port or a range of ports for outgoing connection, the incoming port of your client should not be in this range but you should set it to (a + 1 or a - 1 if a is the outgoing port) or (a - 1 or b + 1 if [a,b] is the outgoing port range).
- With above settings you can create a single QoS rule with these requirements:
 . Local IP range: set both start and end text box to the IP of the box that you will use bittorrent from.
 . Remore IP range: the entire range (the default IPs).
 . Local port range: the range you set your client including the port for incoming connection.
 . Remore port range: the entire range (default ports).
 . Set the priority to what you want for torrent with 255 is the lowest possible priority.
- After that you create two QoS rules to cover whatever not torrent connections to have the priorities you want. If you do not do this the router will classify these connections on its own which the router does pretty good and it won't or I haven't seen this router classify any connection to have priority 255 so all other connection types will have a higher priority if you set your torrent QoS rule priority to 255 or something low enough.

The short answer is you should create a torrent QoS rule to have 255 priority, other connection types should have higher priorities then. Or you can create 3 rules as I said above.

[Xagest]

This is what I currently have on my system

   Name         Priority                               Protocol   
   Bittorrent    255                                   Any

   Local IP Range                                     Local Port Range
   192.168.1.199 to 192.168.1.199              0 to 65535 (grayed out)

   Remote IP Range                                  Remote Port Range
     0.0.0.0 to 255.255.255.255                     0 to 65535 (grayed out)

=========

   Name              Priority                               Protocol   
   EverythingElse  1                                      Any

   Local IP Range                                     Local Port Range
V   192.168.1.1 to 192.168.1.198              0 to 65535 (grayed out)

   Remote IP Range                                  Remote Port Range
     0.0.0.0 to 255.255.255.255                     0 to 65535 (grayed out)

======

Unfortunately, I'm not seeing any change in my internet performance.  Basic web and email, as well as non-torrent downloads are still incredibly slow when the bittorrent is running (they run fine when bittorrent isn't running).

[bigeyes0x0]

I don't see you checked the entry for bittorrent there. But anyway this router does have QoS but it can only prioritize connections and not limit the bandwidth the computer running torrent client from. So when your torrent client runs really fast there's still a chance your line get overloaded with torrent activity. Your best option in this case is to limit download speed in your bittorrent client using scheduler or other mechanism. Another option is to buy a smart switch that has more sophisticated QoS mechanism.

EDIT: You can check if this router connection prioritizer works by going to your router web GUI Status -> Internet Sessions. You should see your torrent connections get priority 255 and other get 1 from your settings.

[Xagest]

The problem I have is that limiting the bittorrent client like that the limit is arbitrary.  With my internet service, my speed during peak hours is 4mbps, while non-peak hours I get 30mbps.  This means that if someone in the house wants to play a game or something, I would have to set the bittorrent to run at a piddly crawl, or I would have to log onto the machine (no monitor or keyboard is connected to it.  I access it through vnc) and disable all the torrents.

And this doesn't just go for bittorrent.  The idea is to try and fairly share the internet connection.  If someone is trying to download 15 files at once, this shouldn't completely drown out the connection and no one else in the household can read their emails.  The example is extreme, but you get the idea.

I looked in the into the logs, it looks like the bittorrent priority is set to 128, while everything else is set to 1.  The QOS rule for the torrent is checked.

[bigeyes0x0]

From your settings and the status page something must be wrong as your torrent connections get priority 128 instead of what it should be 255.

About what you wanna do, I understand but I don't know why it does not work well enough for you. Maybe this router QoS engine is not aggressive enough in throttling by priority and still causes connections overload like you see. It did work for me when I use torrent and play Borderlands. My internet connection is 6Mbps downstream, and I set my client to only allow 3 torrent files to be download at once. I didn't even have to set up any QoS rule to be honest. It just works. So it might be your torrent settings are too aggressive.

IMO, if you know what the peak hours are you can set up your BT client to throttling down your download to an appropriate level so you can still use other services. If the QoS engine in the router is not to your satisfaction you have to go around and try other tricks, there's really no other way. There's little this QoS engine can do really against a congested line. It's basically just tag your outgoing packets with different priorities and send them out in order of priorities with some kind of additional guard so a packet will not stay in the queue forever. Ergo, if there're so many packets your line will still get congested as your bandwidth is limited. It's not a holy grail.

[PeterJvM]

It should work, however there may be another solutıon. There is a program called netlimiter pro 2,
running this on the torrent-pc you can change the up and download speed for the pc in flight.
Go and have a look at www.netlimiter.com it's an affordable piece of software that serves me well.