[Chilli] Period "Reauthorisation"
Johan Meiring
jmeiring at amobia.com
Tue Jun 14 09:34:00 UTC 2011
On 2011/06/14 04:03 AM, Tim White wrote:
> Thanks Royce. I wasn't aware of CoA.
> If I understand this correctly, with accounting updates chilli sends a CoA
> packet (if coaport is defined). However, some googleing also shows
> acctupdate. I'm using FreeRadius, and some of the documentation in the old
> Coova Wiki seems to be gone.
> Any idea which is the better one to do? CoA or acctupdate? Do they both work
> for updating the remaining data/time or is CoA just for disconnects?
> Normally I can find most things with Google, however this topic is eluding
> me. Having the right search terms is helping now, but there seems to be a
> lack of documentation.
>
You need to seperate the issues.
COA/Disconnect is an RFC standard.
acctupdate is not.
You can use either with chilli.
COA/Disconnect
--------------
You get a COA and a Disconnect.
Disconnect would ask the NAS (chillespot) to disconnect the client
COA can modify Authorisation parameters like time left or bandwidth available.
COA/Disconnect is sent from the radius server to the NAS (chilli)
acctupdate
----------
Chilli has implements a second (non RFC way) where the Accounting Reply can
contain similar Radius Attibutes to what a COA packet would contain.
This is for cases where you cannot reach the NAS from the Radius server.
(e.g. the NAS is behind a dynamic nat)
It works very well. (I use it here).
Cheers,
--
Johan Meiring
Amobia Communications
Tel: (0861) AMOBIA / (0861) 266242
Fax: (0861) AMOFAX / (0861) 266329
More information about the Chilli
mailing list