I have tryed the throttle.server and just added the ip list of all our users, it works as expected.
What I really want to do is limit the bandwith so any one user can not take more than 30% of the pipe.
With throttle.server its a global limit, I want to use my whole pipe.
This is not possible nativley with the MWG.
Bandwidth throttling on the MWG will only attempt to limit the bandwidth usage on a per connection basis, this means that it does not take into account all the connections for a specific user as a whole.
So a user could have 1 connection, where you would throttle it down to X kbps.
But the user could open 20 more connections and each of those connections (individually) could be limited to X kbps (20*X=20X kbps), not all 20 connections limited down to X kbps.
Let me know if that makes sense.
Here is other discussions on the topic, as well as the whitepaper:
I meant to add that it is possible using DSCP header marking on the MWG, which essentially is a tcp header that is marked by the MWG, for use upstream from the Web Gateway on a QoS device.