From mboxrd@z Thu Jan  1 00:00:00 1970
From: Georgi Alexandrov <georgi.alexandrov@gmail.com>
Date: Fri, 10 Feb 2006 09:42:24 +0000
Subject: Re: [LARTC] Conceptual question ;-)
Message-Id: <43EC6000.1020700@gmail.com>
MIME-Version: 1
Content-Type: multipart/mixed; boundary="===============1391736553=="
List-Id: <lartc.vger.kernel.org>
References: <43E9B364.3020009@gmail.com>
In-Reply-To: <43E9B364.3020009@gmail.com>
To: lartc@vger.kernel.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1391736553==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigF49FDE9C977992931BD670A7"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigF49FDE9C977992931BD670A7
Content-Type: text/plain; charset=windows-1251
Content-Transfer-Encoding: 7bit

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


--------------enigF49FDE9C977992931BD670A7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD7GAG+ZABwTe0s+4RAqU7AJwN6XZznmXfIXEI21kCSM8YS1P80QCfT2ni
iPyrWTpuYt2aPvjjk1oV6cI=
=ZQdV
-----END PGP SIGNATURE-----

--------------enigF49FDE9C977992931BD670A7--

--===============1391736553==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

--===============1391736553==--