From mboxrd@z Thu Jan 1 00:00:00 1970 From: Georgi Alexandrov Date: Wed, 08 Feb 2006 09:01:24 +0000 Subject: [LARTC] Conceptual question ;-) Message-Id: <43E9B364.3020009@gmail.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============0632867071==" List-Id: To: lartc@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0632867071== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig963BFF5DA96AFB54C05AC793" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig963BFF5DA96AFB54C05AC793 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 7bit ehlo list, I'm willing to shape ppp users e.g. each pppX interface to get XXX kbits I classify traffic going to ppp+ interfaces like this: iptables -t mangle -A POSTROUTING -o ppp+ -j CLASSIFY --set-class 0002:0020 then i have a file which is executed when a ppp inteface is up and first argument parsed to that file ($1) is the ppp number (e.g. 35 for ppp35). it generally looks like this: tc qdisc del dev ppp$1 root tc qdisc add dev ppp$1 root handle 2: htb tc class add dev ppp$1 parent 2: classid 2:2 htb rate XXXkbit tc class add dev ppp$1 parent 2:2 classid 2:20 htb rate XXXkbit tc qdisc add dev ppp$1 parent 2:20 handle 20: sfq perturb 10 The question is, when for example 10 ppp interfaces are up will they each get XXX kbits. -- regards, Georgi Alexandrov Key Server = http://pgp.mit.edu/ :: KeyID = 37B4B3EE Key Fingerprint = E429 BF93 FA67 44E9 B7D4 F89E F990 01C1 37B4 B3EE --------------enig963BFF5DA96AFB54C05AC793 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) iD8DBQFD6bNs+ZABwTe0s+4RAs11AKCMYX5WprFHxKkAfiBy87A5tOY7WQCgmd2U +s3eMEcN+nBaRwSbgsANfuE= =9hPS -----END PGP SIGNATURE----- --------------enig963BFF5DA96AFB54C05AC793-- --===============0632867071== 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 --===============0632867071==--