Help with QoS / Bandwidth Limiting my setup

Discussion in 'Tomato Firmware' started by Rhaikh, Feb 12, 2013.

  1. Rhaikh

    Rhaikh Serious Server Member

    First off, I'm using the Buffalo WHR-HP-G54 not a Linksys, I hope that's ok or not an issue. If there is a better forum for this question, or if it has already been addressed, please let me know.

    My setup is a Motorola Netopia 2210-02-10NA DSL modem. My Buffalo is connected directly to the modem and it's set up as just an access point (No DHCP server). It has 1 wired client and N (usually 2-3) wireless clients.

    I'd like to limit the wireless clients to some portion of available bandwidth for ALL traffic and keep the wired client unlimited. It would also be nice if I could turn this on and off easily.

    Alternatively, I could limit ALL traffic coming out of the Buffalo and set up a switch between the modem and the buffalo and connect the wired client to the switch, if that is necessary.

    Is this possible with Tomato? I have tried messing with QoS and Bandwidth limiter, configuring it more than a few different ways, but I've never demonstrated (by speedtest) that it was doing anything at all.

  2. Monk E. Boy

    Monk E. Boy Network Guru Member

    If your Buffalo isn't running in router mode, with different subnets (e.g. vs. for the Buffalo & Modem networks, then you can't shape traffic at all. If your Buffalo is running in access point mode, it's attached to the same network as the modem, and you can enable all the QoS, BW Limiter, etc. functions you want and it won't have any effect because they only affect routed traffic.

    If you change your network so the Buffalo routes into your modem, I would guess that you'd want to look into either Victek's or Shibby's builds as they have a more effective BW Limiter. QoS affects all traffic flowing through the router on a priority basis, and while you could accomplish exactly what you want with less pain than the plan you intend to implement, its not going to be the same as what you describe. QoS is about prioritizing traffic logically, so you can prioritize one type of traffic over another.
  3. Rhaikh

    Rhaikh Serious Server Member

    Thank you for your reply. I think I've managed to get it all set up now. I am using the latest Shibby build.

    The tricky part, which I recalled halfway through this process as being the reason for my previous setup, was getting the modem and the buffalo router to play well together. I was unable to set it up so that the Buffalo router retrieved DHCP config from the ISP through the modem, so both the modem and the buffalo router had to be set up with a DHCP server on different subnets as you indicate above. Miraculously, I am also able to connect to the web admin page for both devices simultaneously, I remember this being troublesome before. Once all of the Buffalo clients were on their own subnet, using Shibby for bandwidth limiting was trivial and worked!

    Thanks again.
  4. Pentangle

    Pentangle Serious Server Member

    As said above, tomato needs to be routing the traffic. That said, you get the greatest benefits from QoS when a small percentage of the ingress and egress bandwidth is left as headroom irrespective of the method of connection. Hence I would architect things to route through the tomato, measure the bandwidth and set the limiter to about 80-90% of that speed and then set QoS rules for the traffic accordingly. You can then measure and adjust as you see fit.
  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