The patch files name was htb3.3-020512.tgz (means 3.3 ? )
----- Original Message ----- From: "Martin Devera" <[EMAIL PROTECTED]> To: "Muhammed Soyer" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, May 20, 2002 12:35 PM Subject: Re: [LARTC] htb error 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, diff=3938700 >now=1894047744 then=4294959104 j=46368551 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff=3938700 >now=1894072320 then=4294959104 j=46368554 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff=3938700 >now=1894096896 then=4294959104 j=46368557 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff=3938700 >now=1894121472 then=4294959104 j=46368560 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff=3938700 >now=1894146048 then=4294959104 j=46368563 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff=3938700 >now=1894170624 then=4294959104 j=46368566 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff=3938700 >now=1894195200 then=4294959104 j=46368569 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff=3938700 >now=1894219776 then=4294959104 j=46368572 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff=3938700 >now=1894244352 then=4294959104 j=46368575 > May 20 09:40:07 gesrouter kernel: HTB: bad diff in charge, diff=3938700 >now=1894268928 then=4294959104 j=46368578 > > > these messages continue for ever.. > > What can the problem be ? > > > -------------------------------------------------------------------------------- > > Muhammed Soyer > > > > _______________________________________________ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ _______________________________________________ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
