Using QOS - Tutorial and discussion

Thanks, but the OP reports failure with the provided suggestions. I'll keep an eye on it, though.

Edit: I may have mis-read, so nevermind (at least for now).

Would be interested to know which settings may or may not be safe for export/import. I will probably start a new thread when I finish building a list of what looks important to me.

@Toastman
Just curious does VLan gets QOS too or it doesnt?

Forgive my ignorance, aren't VLANs still LANs? QoS is concerned with prioritizing traffic on WAN/Internet bound traffic, not transfers between computers on the internal network.

not really, QoS could be only on main lan. VLan is a virtual lan

I dont see ips from Vlan being filtered so thats why I asked.

As I recall QoS only binds itself to the WAN interface. Or, at least, it only applies to traffic using the WAN port.

If you want to roll your own QoS that applies to VLAN to VLAN traffic you can, but you'll have to do it all by hand... and I don't think it'll show in the GUI. The VLAN builds are flagged as experimental for reasons like this.

Hi Guys,

I've completed / compiled my recommendations and tips based on everything I've learned from here. This is how I proceed to set things up, for the basic settings page. First I delete everything on the classification page, and change all the rulenames.





Remember:

1) Classes on top steal bandwidth from the bottom ones

2) Classes on bottom should have a high maximum (usually 100%), since top ones will steal if they need to.

3) When in doubt, use 1 to 5% minimums in general.

4) The sum of all minimums should not exceed 100%. When in doubt, keep them all low.

5) At your leisure, use larger minimums (10% - 20% perhaps) for some important lower classes, like the default class such that we prevent upper classes from stealing ALL their bandwidth.

6) for your top classes, set low maximums as needed. Typically, gaming and VoIP do not require a large amount of bandwith. Setting a high maximum does not give better latency, and if something malfunctions (misclassified app), the erroneously identified top-class will steal lots of bandwidth from the lower classes.


7) DSL Settings is only for ADSL and ADSL2+. Not needed for cable or VDSL.

----
Classification page
use your own logic, and whenever possible using ports instead of L7 rules. You can verify if your stuff is beingc classified correctly using the graphs and connection details.
-------

I personally would never give my class 1 no limit rule because it can break your whole qos. Say if a few pcs are downloading or streaming or uploading a big file on net it will make your dns latency increase alot and make your voip very laggy. That is of course if you are classifying http and https in class 1.

Yeah but, as he explains, he's not using any of the "No Limit" classes.

I would still make class #1 be a "service" class with high bandwidth constraints, then assign that to DNS, NTP, etc. traffic. You're going to have a hard time performing VOIP operations without functioning DNS, that's why by default it's the highest priority category with minimal bandwidth assigned to it.

The only time NL makes sense in terms using it in rules is when you assign all categories to be no limit for inbound or outbound. If you want inbound to be unlimited, just set all the categories to no limit.

cloneman:

I don't have much time right now so just a few things:

I don't get why you want to purge everything from the classification page. Those are quite reasonable default filters. I haven't looked at every single one of them, but they seem to work fine. In my oppinion purging the filters is for the absolute pros only. Ok, if you just don't care a lot whether some of traffic ends up in the default class that's fine or you just want to filter by Mac address or something. But as a general rule of thumb purging doesn't make a lot of sense to me.

It's the same with the classes: If you enable "Prioritize SYN/ACK/RST/etc." on Basic Settings there will be traffic in the highest class aka your 1_. I definitely don't recommend messing with this class. I don't even see a reason to reduce the number of used classes. There are scenarios where you want to use classes in a different way. But yours doesn't seem to one of those.

cloneman:

can you post everything you have set on your home network? I wanna compare it to me and see how well is mine set.

Well, my QoS has specific goals only for 4-5 applications, I don't trust having that huge ass ruleset, confuses the hell out of me.... good luck diagnosing lag with 40 rules.

I've never tried to be honest. Figuring out QoS is very complicated i find, I had enough trouble with 3-4 rules. Now that I understand how everything works, I might be tempted to try more stuff, but I'm happy and I figure there's less CPU overhead with less rules?

This is my classification page now (highly draft). I was told I forgot the VoIP RTP port, but it catches it anyway (magic?)



I have my net.outgoing_port and net.outgoing_max_port customized in uTorrent. (7000 - 7005)


Someone asked for my other settings, so I'm posting them as well (nothing too exciting here)

thanks......I'm not trying to accomplish much..just trying to find a best fit model taking here and there to make my own........theres always lag no matter what you play and configure.......

casual web browsing is always fast for me with QOS.....now playing with games like league of legend so its less lag running full utorrent.

Sorry if this has been asked before, but i´m not quite sure what to set for the Inbound, Outbound Rates / Limits.
My Router is connected to my cable modem, which gets 90 mbps download and 6 mbps upload speed (tested with a few speed tests with a direct connection).

There are several computers connected to the router using wlan and because of that the internet speed is at 30 mbps download and 5 mbps pretty much stable ( i couldn´t get the wireless speeds faster than 30 mbps but i´m ok with that).

So do i have to use the 90/6 for the inbound/outbound limits or the 30/5?

Since this is a wireless lan problem i figured i set it to 90/6, is this correct?

So you are saying that you _only_ have wireless clients?

If that's true, then your real bottleneck is your wlan and it might be more reasonable to shape donw to 30/5. On the other hand, if your wireless clients are using servers on you LAN (for backups etc.) then you will still get congestion on your wlan interface no matter how great the 30/5 QoS works. You could shape on your wlan interface additionally. I've never tried this, though, but it's possible.

Did you measure the 90/6 with QoS enabled? Just asking because it's very rare that you actually get these speeds with QoS enabled because QoS is straining the CPU of these small routers immensely and most people get less bandwidth. At this point people usually have to decide if their network get's so congested because of many users who use p2p (as an example) that they think they might still profit from less bandwidth but less congestion with QoS enabled or just disable QoS because their network does not have problematic users and doesn't get congested easily.

Is it 30mbps total with multiple clients active (I assume), or 30mbps from a single client? It's the total throughput in the LAN-WAN interface that you are shaping with Tomato QoS.

You will be subject to latency spikes due to the bottleneck in the wireless interface regardless of the Tomato QoS settings. You may benefit from reducing txqueuelen to some minimal value on both the router and the clients. There are other changes you could potentially make in the clients depending on the OS involved.