Question about a QoS setup.

Discussion in 'Tomato Firmware' started by robert112, Jul 26, 2009.

  1. robert112

    robert112 LI Guru Member

    I’m using Tomato RAF v1.25.8515.2 ND on a WRTSL54GS and am trying to figure out the best way for my roommates and me to split our internet connection. The QoS in Tomato looks promising but I would like some clarification as how to go about doing it. The internet connection we have is 10mbps/1mbps and needs to be split four ways; a minimum of 30% to three users and 10% for guests. All of us have many devices that access the internet, so the percentages need to apply to each user’s total devices. So far I have set up a static DHCP for each MAC address of our devices, grouped them in ranges per user, and set a DHCP range for guests. In the QoS settings, each person has a 30%, 95% rule (Class A,B,C) for their range. The guest range has a 30%, 50% rule (Class D). Under those rules are the protocol rules (eg web, dns, xbox, bittorrent..). Basically what I want to know is if the ip range filters are being applied before the protocol filters. From the look of the graphs, it doesn’t appear to be working that way. But then again data from the ip ranges and protocols are on the same chart.
  2. Toastman

    Toastman Super Moderator Staff Member Member

    Hi Robert, welcome to the forum

    The rules are applied in order from the top down. Perhaps your IP range rules are not allowing others below them to function. Without seeing your setup, it's difficult to help.

    There are 2 ways to share the bandwidth. The method you are using presently might be better done with the Victek mod's Bandwidth Limiter (the IP/MAC QOS) to place a limit on users (you can still use QOS simultaneously).

    The second method is to use QOS to prioritise applications which will let any user access full (or most) bandwidth if it is not being used for anything more important. This gives the feeling of a fullspeed 10Mbps connection to most users, most of the time - if set up correctly, and is a better solution.

    The thread below may help you to figure out how to use Tomato's QOS effectively.

    Good luck!
  3. robert112

    robert112 LI Guru Member

    Actually I am using Victek's mod. I looked into the IP/MAC BW Limiter but thought it would not work because a range of ips cannot be specified. All three of us have at least 4 devices that can connect to the internet, and I figured it would be easier to guaranty each person gets at minimum 30% no matter which devices they are using.

    Here are some shots of my setup.

  4. Toastman

    Toastman Super Moderator Staff Member Member

    I see what you want to do, and you've modified the default rules as a start. Here's a very quick comment on how you might proceed.

    At the moment it looks like all machines end up in classes ABCD, A will get greater priority than D, which probably isn't what you wanted, and the rules underneath won't be implemented. Also, the method used in the default rules to classify P2P traffic doesn't work well. I don't think it is practical to try to give each user a limit as well as attempt to simultaneously use application priorities, when each user has several clients. It becomes a nightmare. It would probably be better done with a combination of QOS and IP/MAC limiter, but personally I would just try to allow anyone to get full speed when it is available. You really need to play around, and get a feel for what is possible.

    I would conduct a very quick experiment to see if this works for you and get a feel for things. Delete the first 4 rules, plus the bulk, and the P2P.

    Set your default class to say D. Remove rules to try to control P2P with L7 etc filters - they don't work well. Just address other applications you want to prioritise, and the ones you don't address (P2P etc) will automatically bypass your rules and end up in the default class. This way you don't have to try to trap them. Now you can even throttle P2P altogether by setting bandwidth to zero if you wish. Try to address applications by port numbers wherever possible because L7 filters are unreliable and slow (take up a lot of processing power). More than a couple or so L7 filters can often slow your router to a crawl.

    Use your other rules, but spread them out (e.g. - instead of DNS, xbx, skype being in same class, use all of the classes Highest to E. Use "Highest" purely for DNS. Share outgoing bandwidth by protocol, don't let all classes rise to 100% in outgoing flow, set a smaller limit as necessary, it's a must with P2P - try setting 1-10% at first.

    Limit class maximum incoming bandwidth per class in the Incoming bandwidth selection (the one you haven't shown). Set a low limit on incoming bandwidth to improve VOIP latency. Look in the QOS thread for a chart and tips with that.

    I would recommend that you read the thread below thoroughly, because any questions you may have about QOS are probably covered. You can also and copy the setup near the end of that thread, if you wish, it will give you a working base which will show you the principles, and be a good base from which to start.

    If there aren't too many clients in use, by the way, IP/MAC limiter will still work, as it allows a lot of rules - now up to 140 I believe.
  5. robert112

    robert112 LI Guru Member

    The QoS guide was really great. After reading through it it seems that controlling the ports will do just fine. We only have 3 main users, so it should be much easier to shape and control our network as opposed to an entire apartment complex. :thumbup:
  6. Toastman

    Toastman Super Moderator Staff Member Member

    Thanks! And good luck!
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice