Hello Christoph :
Thank you very much for the timely help. Your solution did work, but the
doubt still remains why we should be giving 16384(or 16385bps) when
128Kbps will result in 131072bps !!! 16384 is 128x128 !!! :)
Thank you once again.
Regards,
Vinay.
P.S : I had taken care of classid and the parent id properly. It was just
a typo. Thank you anyways :)
On Thu, 9 Mar 2000, Christoph Mause wrote:
>
> Hi,
> I don't know if this will be a problem, too. But the second tc command
> say that you want to attach class 1:3 to parent 1:1. But there is no
> parent 1:1. The root qdisc has handle 1: which means 1:0.
> So you should try:
>
>
> tc class add dev eth0 parent 1:0 classid 1:3 cbq bandwidth 10Mbit rate \
> 2Mbit allot 1514 weight 1 prio 1 maxburst 20 avpkt 1000
>
> Concerning your problem with the peakrate I tried a few things. I used
> bps instead of Kbit. 128Kbit is 16384bps. That didn't worked as well.
> But when I tried it with a peakrate of 16385 everything worked fine and
> even
>
> tc qdisc ls dev eth0
>
> said that the peakrate is 128Kbit. Don't ask me why. That seems strange
> to me, but it works.
> Here's the line I used:
>
> tc qdisc add dev eth0 parent 1:3 tbf rate 128Kbit burst 10Kbit \
> mtu 380 peakrate 16385bps limit 10Kb
>
> That should work.
>
>
> Bye,
> Christoph
>
-------------------------------------------------------------
Vinay V. Kulkarni
Project Assistant, ERNET, ECE Dept., IISc., Bangalore 560 012
Ph : +91-80-360 0855. Fax : +91-80-360 7991
-------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
