Hi,
Sorry for not answering until now, I have been a bit busy.
> >From looking at your stats output 101 packets (101p stat) on the queue
> sounds like a little bit too many packets to me to be sitting there
> waiting to be serviced.
Yes - I don't claim that it works ;-)
> So that could be your problem 1: Some app is
> hanging somewhere because every packet it sends is just sitting on the
> queue (and perharps never leaves).
Hmmm, this sounds as a possible result rather than a cause of the
problem...
> The other thing that could be happening is that the backup cbq
> watchdog timer does not get activated for some reason -- although i would
> really doubt this because CBQ works very cleanly for me. To test this
> theory, when it hangs, send a few ping packets towards the destination
> node and see if they help clearing up the queue.
Well, it seems like what happens is that at some point no packets are
sent from the que which is then fastly filled.
BUT: I have now tried my setup on a completely different machine with
completely different hardware (it has two DE202 cards controled by the
DEPCA driver) and this time I used the machine as a bridge. I has exactly
the same problem though there was 1 hour and 15 minuttes until it happend.
So I am more than convinced that this really is a problem with CBQ and my
error seems to be very easy to reproduce.
Christian
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
