Setting bandwidth rules to just put one computer into the crawl class

Discussion in 'Tomato Firmware' started by fefrie, May 17, 2018.

  1. fefrie

    fefrie Networkin' Nut Member

    Bandwidth limiter isn't working as great as I want it to. It's not putting one specific computer in to the LOW class.

    If I have 3 computers, on in low, one in medium, and one in high, all with similar limits to account for overhead.

    Never really worked that great, never really could tell how the bandwidth was being dividided, and I generally prefer the realtime monitoring of QOS which seemed to work really well.

    I could simply just place any traffic from the low computer into the crawl class and leave the rest of the settings as is.

    But I'd like to try to simplify the rules (because I have only a 250mhz cpu) so that I have the low computer in the crawl class, and everything else as the standard class (www), where all traffic just shares as is, as needed.

    Is my logic sound in assuming that having only 2 or three classification rules is 'easier'

    [is it this rule? What about the next? What about the next? What about the next? What about the next? What about the next?],

    or does it not really matter and it's just simply [column a, row b goes to column B , row g] and it's fine to leave all the rule classificaitons in place.

    How would I set a classification rule that captures ALL traffic from ALL computers except for 1 computer?

    Or..... set the LOW computer to the crawl class as my one and only single rule, and set the default class as www/voip, or any other high level class.....

    Lastly, which one is the one with all the classification rules? I think it would be good to make a backup of it....

    nvram export --set | grep rrule (or rrule1 - and so on)
    nvram export --set | grep qos
    nvram export --set | grep qos_
    nvram export --set | grep qosl
    nvram export --set | grep qos_orules

    What about the next?

    Thanks everybody. I can't believe I've been here for so long....
  2. Monk E. Boy

    Monk E. Boy Network Guru Member

    Give the system you want crawl'd a fixed DHCP lease. Create QoS rules that says traffic to that address or from that address get placed into crawl. If you totally don't care about the rest of QoS then just dump all the other rules, then change the default class to whatever you've called category 1 or 2. So QoS rules says traffic to and from your one device is crawl and all other traffic gets caught by the default class.

    I'd just set it up from the GUI instead of resorting to Terminal. Deleting all the default QoS rules is a bit of a pain but you only have to do it once.
  3. Mercjoe

    Mercjoe Network Guru Member

    just make
    Just make sure that the rule created is at the top of the list. That way ANY traffic to that address it sent to crawl first.

    Monk E. Boy, can you not just use the MAC address instead of a fixed IP?
  4. Monk E. Boy

    Monk E. Boy Network Guru Member

    You can use MAC addresses as the source but not the destination, at least using the website. I prefer to classify traffic flowing both ways, since I believe port forwarded traffic can end up being classified as to that IP not from that IP.

    If your worry is that they're going to manually assign another IP, use the "bound to" option in basic->dhcp on their lease, that will prevent the router's arp from recognizing that mac with a different IP. They could talk to local systems with a different manual IP (can't affect arp on all systems) but they won't get through the router. I haven't played with it in years though so my memory might be a little fuzzy.
  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