[Chilli] stresstest coova chilli

[Johan Meiring]

On 2011/06/03 12:39 PM, Peter Warasin wrote:
> hi guys
>
> Is there someone which already did stress test coova chilli?
>
> We currently face an odd problem, where under unknown random
> circumstances a user which is successfully logged out in chilli remains
> online within radius. This is quite impossible to reproduce and
> therefore I would stress test chilli.
>
> However the setup is way to complex to simulate hundreds/thousands of
> users. What I would like to try now is to split chilli in subproblems
> making it possible to enable/disable them at will and then test the
> subproblems.
>
> Anyone already did such a thing? Or does someone have suggestions how to
> simulate many users?
>

This is a radius problem and not coova chilli.

This is quite normal.
Radius packets are UDP and can easily get lost (especially with lots of clients)

You need to make your radius server able to handle lost accounting packets.

e.g.
Lets say your interim accountint update is set to 5 minutes.
Every time you receive an accounting packet, update a "last seen" field.

Run a cron job every 5 minutes that "closes" sessions (sets accounting stop 
time to something other than null) where the "last seen" field is older than 
15 minutes.

Hope this makes sense.

Cheers,

-- 


Johan Meiring
Amobia Communications
Tel: (0861) AMOBIA / (0861) 266242
Fax: (0861) AMOFAX / (0861) 266329