All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Maciel Fonseca bruno@avati.com.br
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Traffic Shapping
Date: Tue, 09 Jan 2001 10:53:11 +0000	[thread overview]
Message-ID: <marc-lartc-98373940416842@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416837@msgid-missing>

<PRE>Hi,
	I've done some tests with some differents implementations, here are some 
problems and solutions :), I had..
	 First I tried to use my first script to limit the outgoing traffic (with 
little changes) :

tc qdisc add dev eth0 root handle 1:0 cbq bandwidth 256Kbit avpkt 1000
tc class add dev eth0 parent 1:0 classid 1:1 cbq bandwidth 256Kbit rate \ 
64Kbit allot 1514 weight 6Kbit prio 8 maxburst 20 avpkt 1000
tc class add dev eth0 parent 1:1 classid 1:11 cbq bandwidth 256Kbit rate \ 
64Kbit allot 1514 weight 6Kbit prio 5 maxburst 20 avpkt 1000 split 1:1
tc qdisc add dev eth0 parent 1:11 sfq quantum 1514b perturb 15
tc filter add dev eth0 parent 1:0 protocol ip prio 100 handle 1 fw classid \
1:11

	As I know it didn't work. For me it was normal because I've done many tests 
with it... Then I decided to change the line you told me was wrong, so I used 
this script: 

tc qdisc add dev eth0 root handle 1:0 cbq bandwidth 256Kbit avpkt 1000
tc class add dev eth0 parent 1:0 classid 1:1 cbq bandwidth 256Kbit rate \ 
64Kbit allot 1514 weight 6Kbit prio 8 maxburst 20 avpkt 1000
tc class add dev eth0 parent 1:1 classid 1:11 cbq bandwidth 256Kbit rate \ 
64Kbit allot 1514 weight 6Kbit prio 5 maxburst 20 avpkt 1000 bounded
tc qdisc add dev eth0 parent 1:11 sfq quantum 1514b perturb 15
tc filter add dev eth0 parent 1:0 protocol ip prio 100 handle 1 fw classid \
1:11

	And again it didn't work. Then I remembered that you told me that tbf is 
better than sfq to use, so I used that last script changing the sfq's line to:

tc qdisc add dev eth0 parent 1:11 tbf rate 64kbit buffer 10Kb/8 limit 15Kb 
\mtu 1500

	So it work as I've known (because I've tested a script like that an it 
worked).
	Then to a final test I changed back the bounded to split in the third line 
and it limited the traffic.
	After all, my doubt is if the problem is the sfq, because tbf worked 
perfectily (in the two cases!!). So if you or someone has a good 
documentation about the both please send me...

thanks a lot,
	Bruno


On Monday 08 January 2001 16:47, you wrote:
&gt;<i> Your welcome.  I glad to hear that :)
</I>&gt;<i> It should work, if it don't work, then I will be wondering too :)
</I>&gt;<i>
</I>&gt;<i> Hey.. I tried to analyze your first script that use with ipchains fw too.
</I>&gt;<i> Maybe the wrong command is at this command:
</I>&gt;<i>
</I>&gt;<i> tc class add dev eth0 parent 1:2 classid 1:11 cbq bandwidth 128Kbit rate
</I>&gt;<i> 128Kbit allot 1514 weight 2Kbit prio 5 maxburst 20 avpkt 1000 split 1:2
</I>&gt;<i>
</I>&gt;<i> I think if you use 'split', your filtered client (ip 10.0.5.2) can still
</I>&gt;<i> use reserve bandwidth if it's the only client used the traffic at that
</I>&gt;<i> time. But if you use 'bounded', the traffic of filtered client will be
</I>&gt;<i> strictly bounded at that rate.
</I>&gt;<i> Please tried your first outgoing script with ipchains fw with another
</I>&gt;<i> client that use the traffic too.
</I>&gt;<i> I'm still learning this things too, so let me know if it doesn't work.
</I>&gt;<i> I'm glad that I can learn this QoS with you.
</I>&gt;<i>
</I>&gt;<i> Best Regards,
</I>&gt;<i> Junus Junarto D.
</I>

</PRE>

      reply	other threads:[~2001-01-09 10:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 17:22 [LARTC] Re: Traffic Shapping Junus
2001-01-09 10:53 ` Bruno [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-98373940416842@msgid-missing \
    --to=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.