How to rate shaping per user or ip address?

Hi,

 

 

you can do that with an iRule. Have a look at this.

 

 

http://devcentral.f5.com/wiki/iRules.rateclass.ashx

 

 

It contains an example how to do that.

 

 

Regards

 

Kurt Knochner

Kurt,

 

Thank you for your reply. All the iRule solution I have looked at requires to specify ip address of the client or subnet ip address then put them into a rate class, which is not what we want.

 

What we want is to apply single rate to all users and limit them to that rate per ip address, let's say 5M per ip address, every ip address should be able to get 5M as long as we have the capacity. Is there any way to do that?

 

Thanks,

 

 

Yatao

 

Yatao,

 

 

let's see if I understand that correctly.

 

 

There are 10 concurrent TCP connections, each originating from a different IP address. Each of these connections shall get 5Mps. Is that correct?

 

 

Regards

 

Kurt Knochner

yes. Or however many user, each user should not exceed 5Mbps.

 

 

Thank you for your help,

 

 

Yatao

 

Anyone has any idea whether there is any way to achieve this in LTM?

Did you get a solution to this?

Joining to above question, any solution for that?

 

 

Thanks.

Believe it or not this should work per connection, I'm just not sure if it'll work for the combination of all connections for a client or each connection;

when CLIENT_ACCEPTED {
 rateclass rc-name
}

Hi,

 

Actually what that you are saying is that if I configured rate class to 512 Kbps then all connection from each client will be shaped to 512 Kbps?

 

for example all connection from source IP X will be shaped to 512 Kbps and all connection from Client Y will be shaped to 512 Kbps and so on and not as a cumulative shaping to all clients?

 

 

Thanks.

Well what I'm not sure about is whether it would apply to each connection from each client individually or all connections from each client combined. Can't seem to find much information on Rate Classes when applied by iRule. Regardless, changing the event to SERVER_DATA might be an idea, I guess it depends on where you want to limit, client to server or server to client?