There should be no difference in using Expiration and
WISPr-Session-Terminate-Time in this case. Expiration sets
Session-Timeout and ChilliSpot knows that one. The only difference is
that Expiration will work with wired connections too.
Kalik Informatika ISP
Dana 10/3/2007, "Internet-Wifi Operador" <[EMAIL PROTECTED]>
>If you use Chillispot, put in your user
>Max-All-Session and WISPr-Session-Terminate-Time they work very good
>because if you use Expire attribute the freeradius know it but chillispot
>no, so if the user try to connect after the Expire time the radius reject
>this connection, but i the user is connected and the chillispot don't know
>the expire attribute so the connection continue.
>here is the suported attributes for the chillispot
>>From: PD <[EMAIL PROTECTED]>
>>Reply-To: FreeRadius users mailing list
>>To: "FreeRadius users mailing list" <email@example.com>
>>Subject: Re: FR supported attributes
>>Date: Sat, 10 Mar 2007 03:46:50 +0000
>>Unfortunatelly, I found the answer of the similar question.
>>Well.. just to make sure, can Expiration attribute work together with
>>Max-All-Session attribute ?
>>The case is suppose to create an account for 10 hours but only valid one
>>week after the creation date.
>>On 3/10/2007, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>> >Radius attributes - http://www.freeradius.org/rfc/attributes.html .
>> >You actually invent sqlcounter attributes yourself by making the
>> >appropriate SQL query.
>> >Ivan Kalik
>> >Kalik Informatika ISP
>>List info/subscribe/unsubscribe? See
>Get a FREE Web site, company branded e-mail and more from Microsoft Office
>List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html