From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Devera Date: Mon, 20 May 2002 09:35:32 +0000 Subject: Re: [LARTC] htb error Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org Hello, what HTB version are you using ? On Mon, 20 May 2002, Muhammed Soyer wrote: > Hi, > I am tryin to shape my routers traffic ..I have read lartc document .HTB is suggested there .So I used htb ..My kernel is 2.4.18 .I patched my kernel and activated the supports .. > I have created my classes as follows > > tc qdisc add dev eth2 root handle 1: htb default 14 > tc class add dev eth2 parent 1: classid 1:1 htb rate 2mbit ceil 2mbit > tc class add dev eth2 parent 1:1 classid 1:10 htb rate 700kbit ceil 1700kbit > tc class add dev eth2 parent 1:1 classid 1:11 htb rate 200kbit ceil 1250kbit > tc class add dev eth2 parent 1:1 classid 1:12 htb rate 600kbit ceil 1700kbit > tc class add dev eth2 parent 1:1 classid 1:13 htb rate 200kbit ceil 1700kbit > tc class add dev eth2 parent 1:1 classid 1:14 htb rate 300kbit ceil 1700kbit > > tc qdisc add dev eth2 parent 1:10 handle 10: sfq perturb 10 > tc qdisc add dev eth2 parent 1:11 handle 20: sfq perturb 10 > tc qdisc add dev eth2 parent 1:12 handle 30: sfq perturb 10 > tc qdisc add dev eth2 parent 1:13 handle 40: sfq perturb 10 > tc qdisc add dev eth2 parent 1:14 handle 50: sfq perturb 10 > > tc filter add dev eth2 protocol ip parent 1:0 prio 1 u32 match ip dst 194.x.x.254 match ip sport 80 0xffff flowid 1:10 > tc filter add dev eth2 protocol ip parent 1:0 prio 1 u32 match ip dst 194.x.x.254 flowid 1:11 > tc filter add dev eth2 protocol ip parent 1:0 prio 1 u32 match ip dst 194.x.x.250 flowid 1:12 > tc filter add dev eth2 protocol ip parent 1:0 prio 1 u32 match ip dst 194.x.x.200 flowid 1:13 > > At the begining every thing works fine ..But when overlimits begins to occur the class having overlimits hangs the traffic related to that class > I have got error messages in syslog as follows > > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff938700 now94047744 thenB94959104 jF368551 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff938700 now94072320 thenB94959104 jF368554 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff938700 now94096896 thenB94959104 jF368557 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff938700 now94121472 thenB94959104 jF368560 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff938700 now94146048 thenB94959104 jF368563 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff938700 now94170624 thenB94959104 jF368566 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff938700 now94195200 thenB94959104 jF368569 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff938700 now94219776 thenB94959104 jF368572 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff938700 now94244352 thenB94959104 jF368575 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff938700 now94268928 thenB94959104 jF368578 > > > these messages continue for ever.. > > What can the problem be ? > > > -------------------------------------------------------------------------------- > > Muhammed Soyer > > > > _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/