From: "hiphin" Date: Wed, 06 Apr 2005 08:08:40 +0000 Subject: Re: [LARTC] ppp+vpn+htb Message-Id: <001701c53a7f$ddcd3d00$0200a8c0@racunar02> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============1435875163==" List-Id: References: <000a01c53a31$16b0ef30$0200a8c0@racunar02> In-Reply-To: <000a01c53a31$16b0ef30$0200a8c0@racunar02> To: lartc@vger.kernel.org This is a multi-part message in MIME format. --===============1435875163== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01C53A90.9B5DE210" This is a multi-part message in MIME format. ------=_NextPart_000_0014_01C53A90.9B5DE210 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Wang,... >Because ppp traffic is over your real network link, you can control ppp >traffic over that physic device. But I think it have limitation, = because >with this way you can't look into the ppp layer and differential >TCP/IP applications encapsulated in ppp layer yes, that is my question, if I control eth0 only, I can not have per = user=20 limmiting... can I do something simple like this: /sbin/tc qdisc add dev eth0 root handle 1: htb default 10 /sbin/tc class add dev eth0 parent 1: classid 1:1 htb rate 256kbit /sbin/tc class add dev ppp0 parent 1:1 classid 1:10 htb rate 32kbit ceil = \ 256kbit prio 1 burst 64kbit cburst 96kbit /sbin/tc filter add dev ppp0 protocol ip parent 1:0 prio 1 u32 match ip = dest=20 \ $REMOTEIP0 folow 1:10 /sbin/tc class add dev ppp1 parent 1:1 classid 1:20 htb rate 32kbit ceil = \ 256kbit prio 1 burst 64kbit cburst 96kbit /sbin/tc filter add dev ppp1 protocol ip parent 1:0 prio 1 u32 match ip = dest=20 \ $REMOTEIP1 folow 1:20 ... or IMQ must be involved... there must be way, to do bandwidth sharing throught vpn-ppp connections thanks=20 ------=_NextPart_000_0014_01C53A90.9B5DE210 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi=20 Wang,...

>Because ppp traffic is over your real network link, = you can=20 control ppp
>traffic over that physic device. But I think it have=20 limitation, because
>with this way you can't look into the ppp = layer and=20 differential
>TCP/IP applications encapsulated in ppp = layer

yes,=20 that is my question, if I control eth0 only, I can not have per user=20
limmiting...

can I do something simple like=20 this:

/sbin/tc qdisc add dev eth0 root handle 1: htb default=20 10
/sbin/tc class add dev eth0 parent 1: classid 1:1 htb rate=20 256kbit

/sbin/tc class add dev ppp0 parent 1:1 classid 1:10 htb = rate=20 32kbit ceil \
   256kbit prio 1 burst 64kbit cburst=20 96kbit
/sbin/tc filter add dev ppp0 protocol ip parent 1:0 prio 1 u32 = match=20 ip dest
\
   $REMOTEIP0 folow 1:10

/sbin/tc = class add=20 dev ppp1 parent 1:1 classid 1:20 htb rate 32kbit ceil \
   = 256kbit=20 prio 1 burst 64kbit cburst 96kbit
/sbin/tc filter add dev ppp1 = protocol ip=20 parent 1:0 prio 1 u32 match ip dest
\
   $REMOTEIP1 = folow=20 1:20

...

or IMQ must be=20 involved...
there must be=20 way, to do bandwidth sharing throught vpn-ppp connections

thanks=20



------=_NextPart_000_0014_01C53A90.9B5DE210-- --===============1435875163== 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 --===============1435875163==--