Thanks Alan. My expiration attribute is now working To add more details, the OP field must be set to "==" and not ":=" and it worked smoothly.
The next challenge for a prepaid dialup would be , is there a possibility that an account's expiration would be modified, using MsSQL queries inside sqlcounter.conf, on the first successful authentication For Ex. An prepaid dialup card is to expire within 30 days starting May 1, but the user who bought it used the prepaid dialup account on the May 29, is there an attribute that will modify or prolong the expiration for 29 days more since it was used successfully on the 29th day of the month, therefore activating the dialup account on the first successful usage. I hope I made my point clear here. Anyone? ----- Original Message ----- From: "Alan DeKok" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 20, 2004 3:41 PM Subject: Re: expiration attribute > "Milver S. Nisay" <[EMAIL PROTECTED]> wrote: > > i have inserted expiration attribute with radcheck table, with a PAP account > > as shown below > > | 243 | milver | Expiration | := | 20040419153024 | > > That isn't a date. It's simply a long number. > > > but if i manipulate the expiration attribute to a date which has expired or > > past already, > > authentication STILL seems to go, nothing changed, the account can still > > logon with freeradius. > > No, you edit the Expiration to have another value, which still isn't > a date. > > In the 0.9.3 release, try "01 Jan 2004". In the CVS snapshots, you > can use HH:MM:SS, too. > > Alan DeKok. > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
