Tomato should i enable qos

Are you ready? Locate the closest server in your region and begin the test. Write down your upload speed and download speed. You may need to convert these numbers before they can be added to the QoS settings. In fact, Speedtest. If it displays your speed in Mbps, you must multiply the number by to determine the kilobits per second. TIP: Run the speedtest three 3 times and use the average upload speed and download speed.

For example:. This must be done for both inbound and outbound rates this screenshot only shows inbound rates. On the left, set the least amount of bandwidth to be used. Highest getting the first priority and High the second and so on.

Class bandwidth defines how much available upload bandwidth traffic will be assigned for that specific Priority Class to use. Class and bandwidth are independent factors. Importantly, the Max Bandwidth should be set as a percentage of your average actual upload bandwidth.

Classifications using IP address or protocol require much less processing power than using L7 layer 7 application filter based. Be cautious about using numerous processor intensive L7-based rules which could result in the router unable to process all the information and become overstressed causing issues. An example of Outbound QoS classifications in Tomato router. QoS for VoIP can make choppy calls stay clear and prevent other applications from stepping on the voice. Tomato firmware flashed on a router Linksys WRT54G has some of the best QoS configurations, as well as great graphical displays available for a low cost.

This information about Tomato QoS is very fundamental and should only act as an overview. What works best for any particular network is what is tested and experimented with. Don't need live help? Submit a ticket instead. QoS Qualty of Service Configuration Initial Preparation In order to set up wireless access on a Tomato router, you will first need to access the router itself, you can do this by typing in the IP address of the router into your web browser.

Creating Classifications Navigate to the QoS tab on the left side. You really do need to err on the low side to be absolutely certain that the downlink does NOT become saturated, or the QOS will break. I will discuss the pros and cons of increasing this setting to enable us to download more P2P later. We will show then how to use incoming traffic limits to allow this.

But for the moment, stay with me. You have to decide on a compromise setting that allows higher P2P activity while still allowing a reasonably quick response to priority traffic like HTTP.

These packets no longer have exclusive access to the router's buffers, and since they have no special priority in the queue, may be delayed. Now your downloads will also slow down and can no longer reach the normal speed - they may even drop down to almost nothing. At this point you might think there is something wrong with QOS. But QOS is actually working correctly, and it is your understanding of how P2P operates and your application of the rules that is in question.

Your uploads have dominated the connection because you didn't anticipate what might happen italic text. You allowed uploading seeds to dominate your connection, when what you really wanted to do was to allow downloads. So remember that when you deal with P2P, and decide what is your aim. So how does this work? The connection tracking section of the router firmware keeps a record of all outgoing P2P TCP packets and then attempts to keep a tally on any incoming TCP packets associated with it.

It can therefore add them all up and then calculate the speed of the incoming P2P, which can then be limited. So we could, for example, set an incoming limit on our connection of something under 2 Mbps. If this is exceeded, the router will drop packets italic text , forcing the sender to back off and resend the data — once again allowing the link to stabilize.

It is an attempt to slow down the link before it becomes saturated. If it is allowed to saturate, then it's too late - your QOS isn't working. This is a good time to mention something about the maximum setting in Tomato's incoming limit settings.

Please note that the "Maximum" figure that we set in the incoming category is NOT in itself a limit. There is no overall limit in Tomato. This figure is just used to calculate the percentages of the individual classes. However, you will quickly realize that the sum of these classes can now add up to more than the bandwidth that we have available!

In short - Tomato's QOS incoming bandwidth limiter is fundamentally flawed. Because of this, if you run a busy network, you've probably noticed that in practice it is actually unable to keep the incoming data pegged low. Heavy traffic on a couple of classes may well exceed the total bandwidth available.

But if we do that - we end up with quite low throughput on some of our classes - they can't use all of the bandwidth. Tomato's QOS is unfinished! Now, these figures we are bandying about are not cast in stone. While a link is busily "stabilizing itself", new connections are constantly being opened by WWW, Mail, Messenger, and especially other P2P seeders, while other connections may close unpredictably, and that upsets the whole thing. The goalposts are constantly moving!

You will see from this that P2P in particular is very difficult to accurately control. Over a period, the average should approximate the limit figures. Best latency is achieved with a combination of 1 and 2. Juggling them to accomplish what you want is an art. These graphs of the latency of a 1.

Now let's add some additional information onto the first graph. You can see that ping response begins to be affected from 1Mbps pwards, even at 1.

Set it only when all else has been adjusted and you can see if your outgoing settings are causing congestion. If you try to set up your QOS with incoming limits set, it will actually make it rather difficult for you to see what is happening as a result of your settings, because the limit will kick in and mask what is going on.

Initially, it is useful to set the incoming overall limit to so that it is in effect switched off, this will make things easier for you while examining your graphs and adjusting your QOS parameters.

To recap - For best throughput and reasonable response times and speeds, set incoming class limits quite high if you wish. For best latency, set incoming limits lower. If your router crashes or becomes unstable due to P2P applications opening large numbers of connections, try to limit the number of ports that a user can open. Check that function before adding another rule. You may list the iptables rules by telnet to the router and issuing the command "iptables -L" ["-vnL" for verbose output] or "iptables -t nat -vnL".

If you are running a recent tomato mod, you can also do this from the "system" command line entry box, which is much more convenient. Now an explanation. This therefore places a limit on the connections to the outside from each client on your network.

Without this limit, the router can still be overloaded by incoming P2P etc. Placing limits into either of these chains, which is usually recommended, does work , but in the event of a "real" DOS attack or SMTP mail trojan, the router often instantly reboots without so much as a single entry in the logs. Following much investigation and discussion with phuque99 on Linksysinfo.

The router seems to stay up and running. The next script is to prevent a machine with a virus from opening thousands of connections too quickly and taking up our bandwidth. I don't like this much, because it can prevent a lot of things working properly. Use with caution and adjust the figures to suit your setup. NOTE If you test the above scripts with a limit of say 5 connections in the line, you will often see that it doesn't appear to be working, you will have many more connections than your limit, maybe , that you can't explain.

Some of these may be old connections that have not yet timed out, and waiting for a while will fix it. You should disable it on your PC by command line:.

If your router becomes unstable, perhaps freezing or rebooting, apparently randomly, then it may have been asked to open too many connections, filling the connection tracking table and running the router low on memory. Often this can happen because poorly behaved applications usually P2P clients can attempt to open thousands of connections, mostly UDP, in a short space of time, just a few seconds.

The router often does not record these "connection storms" in the logs, because it runs out of memory and crashes before it has time to do so. Obviously, there is a flaw in the firmware, which most definitely should never allow this situation to happen.

Until such time as we can correct this situation, we must resort to some means of damage prevention and control. Setting the number of allowed connections high say makes the situation worse.