From: Colin Barber (Colin.Barber@xxxxxxxxxxxxxx)
Date: Thu Aug 01 2002 - 08:22:04 GMT-3
CBWFQ will not limit traffic to 128K. It only starts to work under
congestion. If the Ethernet is not congested then www traffic would be
allowed to exceed the 128K limit.
-----Original Message-----
From: Tommy C [mailto:tkc9789@hotmail.com]
Sent: 31 July 2002 23:53
To: jasonwydra@yahoo.com; ccielab@groupstudy.com
Subject: Re: Rate limit (interface command)
Why not consider CBWFQ instead?
Tommy
>From: Jason Wydra <jasonwydra@yahoo.com>
>Reply-To: Jason Wydra <jasonwydra@yahoo.com>
>To: ccielab@groupstudy.com
>Subject: Rate limit (interface command)
>Date: Tue, 30 Jul 2002 21:35:47 -0700 (PDT)
>
>I'm doing a lab that requires rate limiting on Ethernet 0 to block any
>input www traffic that exceeds 128K. The lab does not say that I should
>allow any burst. The rate limit command does not allow you to enter a "0"
>value for normal or ecess burst. Therefore I have to allow at least 1000
>normal burst bytes and 2000 excess burst bytes. 1000 and 2000 is as low as
>it will let me go. Does anyone know a way around this or a reason why it
>works this way? Here is the command below under my Ethernet interface. The
>only way I can see getting around this is lowering the allowable bps from
>128000 down to 104000 so that when yo add up the normal and excess burst it
>will equal 128000.
>
>rate-limit input access-group 100 128000 1000 2000 conform-action transmit
>exceed-action drop
>
>Thanks,
>
>Jason
>
>
>
>---------------------------------
>Do You Yahoo!?
>Yahoo! Health - Feel better, live better
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:13 GMT-3