Feature Request: QOS for HTTP traffic depending on size

[Lucky75]

Hey,

I was wondering if it were possible to throttle traffic that's going through the same port if it's one large continuous file?

QoS works great on throttling applications that use specific ports, but it doesn't really help for someone who's downloading a 4 GB file from a website. Clearly something that is that large shouldn't have as high a priority as a web page loading.

Could that traffic be throttled the longer it is downloading or something along those lines? I know it would be pretty hard to determine the size of the file from the beginning without inspecting packets, but perhaps many packets from the same source would be a sign of a large file that can be continuously reduced in speed up to a certain threshold or something if other, higher priority requests are there at the same time?

[Eric]

This isn't possible with the current implementation, but itt's theoretically possible if the transfer is a single TCP connection (vs UDP or something like bittorrent with multiple connections being used to download one file). There's a connbytes match in iptables which matches the amount transferred in a given TCP connection.

Of course if you ARE dealing with bittorrent you can just use the l7 bittorrent match which IS included.

[Lucky75]

Yeah, I was thinking just people downloading from say rapidshare or some newsgroup or something.

[DoesItMatter]

http://www.hawkingtech.com/products/pro ... ProdID=216

See if you can find one of those.

I do quite a bit of news-group stuff and on one of my internets,
I threw that device on it, and wow, it handles the traffic VERY
nicely and balances out the load with no interaction required.

I found one on E-bay, they should have some listed depending
on where you live.

Great device.