From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] configuration
Date: Thu, 24 Jan 2002 09:53:27 +0000 [thread overview]
Message-ID: <marc-lartc-101186606223053@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101186217614209@msgid-missing>
> Each class or collection of classes should not use receive less than a certain
> assigned bandwidth if they need it.
>
> In the same time I want to make sure that each indvidual IP address in these
> classes has it's own restrictions: that is a minimum B/W (if available),
> maximum bandwidth, burst. Is this possible using HTB? From the documentation I
> see that only leaf nodes can have filters - does this mean that I cannot create
> and apply a filter for a whole class?
Sure it is possible. At the first it is not true that only leaves can
have filters. The opposite it true - only leaves can't have filters.
Filter can be attached to root (qdisc itself) or inner class.
So that you can for example attach fwmark filter without any rules
to the root of HTB.
Then you can control assigning of IP->class in iptables.
You will end up with one inner class for each group of ip and each
"restricted" ip will have then leaf under the inner class. Like:
ROOT 256k
CLASS1(192.168.1.x) 128k
CLASS11(192.168.1.2) 10k
CLASS19(others 192.168.1.x) 118k
CLASS2(192.168.2.x) 128k
CLASS21(192.168.2.2) 10k
CLASS22(192.168.2.3) 10k
CLASS29(others 192.168.2.x) 108k
You probably caught it.
devik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2002-01-24 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 8:51 [LARTC] configuration Sebastian Taralunga
2002-01-24 9:53 ` Martin Devera [this message]
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-101186606223053@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.