From: Georgi Alexandrov <georgi.alexandrov@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Conceptual question ;-)
Date: Fri, 10 Feb 2006 09:42:24 +0000 [thread overview]
Message-ID: <43EC6000.1020700@gmail.com> (raw)
In-Reply-To: <43E9B364.3020009@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1667 bytes --]
Jody Shumaker wrote:
> I don't believe -j CLASSIFY targte can target sub-classes. Pretty
> sure you can only target classes whose parent is the root class of the
> qdisc. You would need to use tc filters to do this, or get rid of your
> redundant classes. For THB for some reason you have a root class and
> a child class with the same limit? This makes no sense, you'd be fine
> with just the 2:2 class and attaching the sfq to that, and setting the
> classify to that.
>
> Otherwise, yes I think this would work in setting a limit on those ppp
> devices as they come up to XXXkbit of bandwidth.
>
> - Jody
Actually it looks like it can target sub-classes:
pppoe users ----- eth1-gw/router-eth0 ----- WAN/Internet
For shaping pppoe users upload i do the following:
attached a root qdisc to eth0
then attached a htb class to it (1:10 for example)
Then i attach dynamicaly classes to 1:10 with numbers (1:91 for ppp1 for
example) with parent 1:10. There are also dynamic iptables rules (alot
of dynamic stuff going on .. lol ;) saying "traffic from that pppoe user
going out trough eth0 CLASSIFY as 1:91"
When a ppp43 is up, a class 1:943 with parent 1:10 will be attached to
eth0 and iptables rule saying traffic from that pppoe user going out
trough eth0 CLASSIFY as 1:943"
and it seems to work fine, upload seems to be shaped at the desired rates.
But that is in a "one pppoe user" test environment, i think it should
work fine when deployed too, and each pppoe user will get their upload
rates ;-)
--
regards,
Georgi Alexandrov
Key Server = http://pgp.mit.edu/ :: KeyID = 37B4B3EE
Key Fingerprint = E429 BF93 FA67 44E9 B7D4 F89E F990 01C1 37B4 B3EE
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-02-10 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 9:01 [LARTC] Conceptual question ;-) Georgi Alexandrov
2006-02-10 9:42 ` Georgi Alexandrov [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=43EC6000.1020700@gmail.com \
--to=georgi.alexandrov@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox