Aren't these variables for submiting to accounting records?
If all of these are usable in the authentication process, why have you
limited the number of variables significantly from what is listed as
being depreciated in a future version?
<SNIP>
The following one-character variables are also defined. However, they
are duplicates of the previous general cases, and are only provided
for backwards compatibility. They may be removed in a future
release.
%a Protocol (SLIP/PPP)
%c Callback-Number
%d request day (DD)
%f Framed IP address
%i Calling Station ID
%l request timestamp
%m request month (MM)
%n NAS IP address
%p Port number
%s Speed (PW_CONNECT_INFO)
%t request in ctime format
%u User name
%A radacct_dir
%C clientname
%D request date (YYYYMMDD)
%L radlog_dir
%M MTU
%R radius_dir
%S request timestamp in SQL format
%T request timestamp in database format
%U Stripped User name
%V Request-Authenticator (Verified/None)
%Y request year (YYYY)
%Z All request attributes except password (must have big
buffer)
<SNIP>
Brian J.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:freeradius-users-admin@;lists.cistron.nl] On Behalf Of
> Alan DeKok
> Sent: Thursday, November 07, 2002 12:10 PM
> To: [EMAIL PROTECTED]
> Subject: Re: MSSQL and FreeRADIUS
>
>
> "Brian Johnson" <[EMAIL PROTECTED]> wrote:
> ?> I am looking to create a completely custom user system
> database backend
> > for FreeRADIUS. I was wondering if there is a doc on the
> variables that
> > may be used in the SQL queries specified in the mssql.conf file.
>
> doc/variables.txt ?
>
> 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
