All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB not working quite the way I'd expect?
Date: Sat, 02 Feb 2002 13:14:45 +0000	[thread overview]
Message-ID: <marc-lartc-101265578016940@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101262785901252@msgid-missing>

>     tc class add dev eth8 parent 1:1 classid 1:10 htb rate 200kbps\
>      ceil 250kbps burst 10k
>     tc filter add dev eth8 protocol ip parent 1: prio 1 u32 match ip\
>      src 199.212.53.0/24 flowid 1:10
>     
>     tc class add dev eth8 parent 1:1 classid 1:11 htb rate 50kbps \
>      ceil 200kbps burst 2k

> So, our residence students are assigned to classid 1:11.  Notice that
> 1:10, our DMZ, is given prio 1, because I want it to get any extra
> bandwidth before our residence.  Indeed, residence users are happily

You did it wrong ! prio 1 attached to filter has to do nothing with 
prio 1 attached to the class. I have a BIG objectives to the overal
filter design in Linux QoS but I can't do anything with it.
Simply add prio 1 to the class definition (last tc line above).
And let me know ! ;)

devik

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  reply	other threads:[~2002-02-02 13:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-02  5:32 [LARTC] HTB not working quite the way I'd expect? Jason Tackaberry
2002-02-02 13:14 ` Martin Devera [this message]
2002-02-03 19:41 ` Jason Tackaberry
2002-02-03 20:20 ` Martin Devera
2002-02-03 21:01 ` Jason Tackaberry
2002-02-03 21:11 ` Jason Tackaberry
2002-02-03 22:25 ` Martin Devera
2002-02-03 22:37 ` Jason Tackaberry
2002-02-04  7:01 ` Martin Devera
2002-02-04 15:04 ` Jason Tackaberry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-101265578016940@msgid-missing \
    --to=devik@cdi.cz \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.