traffic control

Yes, I read on the lartc howto that outgoing data can be shaped and incoming data can be "policed", but that the IMQ driver could be used to shape incoming data. Anyway what I *think* is happening is this:

The IMQ is shaping data, that is, it can just delay what it's being fed. When I was testing my setup, I did it with a local webserver at lan speed. My root qdisc had a rate of 500kbit, but my webserver was planting it at about 100Mbit. When packets are going through the filter, HTB sees that packets for higher priority clients start to get queued, while lower priority clients are just fine. So, HTB starts delaying packets for lower priority clients. So the high priority clients get dequeued and get a higher rate. BUT when I try that in "real life", and a low priority client is already at ceil rate, all HTB sees are packets coming in for high priority, but these packets don't get enqueued because they're coming in slowly, and hence the low priority queue is not touched. I guess then that the solution would be to use 300kbit out of a 1Mbit link and that way things will work, because the queues will start getting full. But of course that doesn't make any sense, buying 1Mbit just to use 300k! I wonder if I use 400k out of 500k, then the traffic bursts in the excess 100k would make the queues start filling?

hjf

-- S’ esta atascado, fuŽrcelo. S’ se rompe, es que necesitaba ser reemplazado.