1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Upload bandwidth limiter not working in Shibby [SOLVED]

Discussion in 'Tomato Firmware' started by jd_hupp, Sep 7, 2014.

  1. jd_hupp

    jd_hupp Network Newbie Member

    On a Linksys E1200 v2 with Shibby 1.28, I'm trying to configure so that one VLAN supports just email and light web browsing. I don't want the default VLAN throttled to any significant degree.

    But to allow Priorities to work, I did enable QoS and set a Max Outbound Bandwidth Limit of 750 (with our measured minimum being around 890), then I set the WWW ceiling to 90%.

    In the VLAN to be throttled with Port 4, I set the Upload Rate and Ceiling to 200. I also temporarily set a D/L Rate and Ceiling to 768 (though currently I have it set to an unreachable 16000).

    Speed testing via Speedtest.net, etc., shows that the temporarily-set Download limits were effective. But the Upload settings were not effective at all (testing at around 900 instead of 200).

    I saw somewhere a recommended workaround for that same problem, to create yet another VLAN with the same setup, remove the port of interest from the existing VLAN and assign it to the newest VLAN. This I did with Port 4. But the problem persisted with the identical setup on the newest VLAN.

    Is this a bug in Shibby, or perhaps a problem in the Linksys hardware, or a configuration mistake on my part?
  2. cloneman

    cloneman Networkin' Nut Member

    Am the only one who's head explodes when reading stuff like this? it's hard to tell because I'm a Linux Networking n00b.

    As far as I know QoS and Bandwith limiter should not be enabled at the same time. Has this changed in recent builds?

    Looks like QoS supports IP ranges. You could enter one in like this SRC IP and set it some low priority, and then setup DHCP so that your guest vlan gets IPs in that range
    Last edited: Sep 7, 2014
  3. jd_hupp

    jd_hupp Network Newbie Member

    In Toastman's QoS tutorial at http://tomatousb.org/tut:using-tomato-s-qos-system , under [2] Setting Your Limits and defining rules for different applications, he writes:
    In the event of huge amounts of traffic occurring which is too much for our bandwidth limitations, we also have to control the maximum amount of data which we attempt to send or receive over those links. This is called “capping”, “bandwidth limiting” or “traffic management”. This is also managed by the QOS system in our router and is a *part* of QOS.​

    In the Shibby interface, the QoS page includes Inbound and Outbound Max Bandwidth Limits. But there is also a Bandwidth Limiter page that provides separately for bandwidth limits per VLAN.

    So in at least this current build, Bandwidth Limits are certainly part of the total QoS approach.
  4. cloneman

    cloneman Networkin' Nut Member

    That guide is out of date - unfortunately people still refer to it. (last edited: 14 May 2011, 21:46 (1211 days ago))
    Several threads on this forum indicate that QoS and Bandwith limiter should not be used at the same time. It *might* work , but there will probably be conflicts.

    As far as QoS goes, the only thing I can suggest is my screenshots and some actual testing to determine what the rules do. https://dl.dropboxusercontent.com/u/570792/screens/dslr/qos_rates_draft.png

    In summary:

    The order of the classes 1-10 is important (1 beats 2, 2 beats 3 etc.)
    The Max for a given class acts as an additional throttling mechanism.
    The minimums prevent upper classes from borrowing too much bandwidth and starving them.
  5. Grimson

    Grimson Networkin' Nut Member

    Yes and no.

    Yes QoS does also function to limit the bandwidth, based on how the traffic is classified and the max rate you configure.

    But the bandwidth limiter page is a separate, more basic, system to just limit the bandwidth on a peer machine/ip base.

    Both do in part the same, so if you enable both of them at the same time they will conflict and "fight" with each other which can cause all kinds of oddities.
  6. jd_hupp

    jd_hupp Network Newbie Member

    Cloneman and Grimson: A THOUSAND THANKS! When I was able to get back to this today, I saw that, between QoS and the Bandwidth Limiter, the latter would be the one to better serve my specific purpose.

    So I disabled QoS, and in the Bandwidth Limiter, for the the VLAN to be throttled, I set the Upload Ceiling to 192 kbps and Priority: Lowest.

    A speed test then confirmed that the Upload Ceiling was working, and that downloads were throttled in the face of heavy Internet activity over the main VLAN.


Share This Page