From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stef Coene Date: Tue, 07 Jan 2003 22:00:09 +0000 Subject: Re: [LARTC] strange htb behaviour Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: lartc@vger.kernel.org On Monday 06 January 2003 07:01, Tobias Geiger wrote: > Hello List, > > I use HTB in a ~80 users serving router with kernel 2.4.20. > > eth0 is the internet interface (half-duplex 1Mbit), > eth1 the internal interface (100Mbit full duplex) > > cause of the fact that the router also serves as a http-proxy (squid) i > thought setting up the default class on eth1 with the real upload-speed > (100Mbit) would do the job, i.e. shaping normal stuff to 1Mbit except > local generated proxy-traffic which should be served with the full > 100Mbit. All other, forwarded, traffic is marked and so filtered to > other classes than the default. > To make it short: It works. when i download s.th. directly from the > server i get the full bw BUT: all other downloads from the internet > absolutly break down and don"t regenerate after some time. i have to > restart the qdiscs! Also i get these strange syslog messages: > > Jan 6 06:39:05 Q kernel: htb*c20007 m=3D2 ty270 c=8311 pq=3D0 df@9600 > ql=3D0 pa=3D0 f: > Jan 6 06:39:05 Q kernel: htb*c20008 m=3D1 t=3D-59999999 cf950 > pq=126192148 df=16359424 ql" pa=10 f: > Jan 6 06:39:10 Q kernel: NET: 77 messages suppressed. > Jan 6 06:39:10 Q kernel: HTB: mindelayP0, report it please ! > Jan 6 06:39:10 Q kernel: htb*g j=126187316 > Jan 6 06:39:10 Q kernel: htb*r7 m=3D0 > Jan 6 06:39:10 Q kernel: htb*r6 m=3D0 > > later also: > > Jan 6 06:40:05 Q kernel: NET: 518 messages suppressed. > Jan 6 06:40:05 Q kernel: HTB: suspicious delay in wait_tree > d=3D-1644459092 cl 008 h=3D1 > Jan 6 06:40:10 Q kernel: NET: 518 messages suppressed. > Jan 6 06:40:10 Q kernel: HTB: suspicious delay in wait_tree > d=3D-1644459092 cl 008 h=3D1 > > > I can't really imagine what causes this strange behaviour, except > perhaps the r2q/quantum settings with which i played around a little > bit, but just because the defaults caused also warning-messages in > syslog. perhaps these r2q/quantum parameters need tuning ?! > I'll attach my shell-script so you can look at it yourself, > thank you very much for any hint. You are not the first one to notice this. But I have no solution/answer. = Maybe Devik does ? Stef --=20 stef.coene@docum.org "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/