Is it possible to use a formatted TIME_STAMP in AcctSQLStatement, like
formatted-date,'%e %m %Y %H:%M:%S'
--
jaws
---
Computer system security is a journey, not a destination
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To
Hello Jaws -
You can only use formatted-date or integer-date (preferably) in an
AcctColumnDef.
See section 6.28.14 in the Radiator 3.6 reference manual
(doc/ref.html).
regards
Hugh
On Friday, Sep 12, 2003, at 09:23 Australia/Melbourne, tracker wrote:
Is it possible to use a formatted
Hmm maybe is problem in too new firmware in my units.
I tell Proxim technicians let they try also test latest firmware 2.3.1
on their
office when 2.2.2 have a working, I dont want to spend time by
trying old Proxim firmware, latest firmware should always work best,
its not my problem, I will wait
On 9/11/03 7:23 PM, tracker [EMAIL PROTECTED] wrote:
Is it possible to use a formatted TIME_STAMP in AcctSQLStatement, like
formatted-date,'%e %m %Y %H:%M:%S'
Easier way may be to have your SQL server insert the time for you. That is,
if your SQL server and your RADIUS server's times are
Hello all,
I want to define global variables for remote radius servers,
their Auth-Port and Radius secret for use in a radius proxy
statement. (I have to change these settings from time to time)
(See the attached radius config below)
Strange things are happening:
Some of the defined global
Hi.
Is it possible to limit the sizes of the logfiles, or can I handle this problem only with external programms or perl hooks? I will also be happy, if I can delete the files, but I think I have to do this with the hooks, too.
My logfiles look like this: %L/Logfile_%Y%m%d
Thx.
Karl Pracher
Hello everyone,
The Radiator 3.3.1 manual states in Section 6.28 AuthBy SQL
AuthBy SQL is tolerant of database failures. If your database
server goes down, Radiator will try to reconnect to a database as
described above, starting again at the first database you
specified.
What does server goes
We are actually running the Avaya 2.2.4 code on our Proxim2000 APs..
Bret
Pavel Paprok wrote:
Hmm maybe is problem in too new firmware in my units.
I tell Proxim technicians let they try also test latest firmware 2.3.1
on their
office when 2.2.2 have a working, I dont want to spend time by
If the radius server cannot make a establish an application level(or below) connection
to the database server, for whatever reason, it will try an alternative, or try again.
If the database gives an error, it seems to me radiator denies the authentication
request but does not assume anything is
Hello William,
On Fri, 12 Sep 2003 01:52 am, William Hernandez wrote:
Hello everyone,
The Radiator 3.3.1 manual states in Section 6.28 AuthBy SQL
AuthBy SQL is tolerant of database failures. If your database
server goes down, Radiator will try to reconnect to a database as
described
Hello all,
On Thu, 11 Sep 2003 10:09 pm, Robert Blayzor wrote:
On 9/11/03 7:23 PM, tracker [EMAIL PROTECTED] wrote:
Is it possible to use a formatted TIME_STAMP in AcctSQLStatement, like
formatted-date,'%e %m %Y %H:%M:%S'
Easier way may be to have your SQL server insert the time for
Hello William -
Database failure means no response to an SQL query (for whatever
reason).
regards
Hugh
On Friday, Sep 12, 2003, at 01:52 Australia/Melbourne, William
Hernandez wrote:
Hello everyone,
The Radiator 3.3.1 manual states in Section 6.28 AuthBy SQL
AuthBy SQL is tolerant of
Hello Karl -
You should use an external cron job or whatever to archive or delete
your log files.
regards
Hugh
On Friday, Sep 12, 2003, at 00:50 Australia/Melbourne, [EMAIL PROTECTED]
wrote:
Hi.
Is it possible to limit the sizes of the logfiles, or can I handle
this problem only with
Hello Stefan -
The port numbers and secret are only evaluated at run time as you have
discovered.
A better method for dealing with multiple, changing radius proxies is
to use the AuthBy SQLRADIUS clause which stores the target details in
an SQL database. See section 6.45 in the Radiator 3.6
On 9/11/03 7:19 PM, Mike McCauley [EMAIL PROTECTED] wrote:
Yes, but you really should take into account the Acct-Delay-Time in accounting
requests, which is the amount of time the request has been sitting in the NAS
waiting for successful transmission. The Timestamp attrtibute takes this into
Hello,
On Fri, 12 Sep 2003 09:49 am, Robert Blayzor wrote:
On 9/11/03 7:19 PM, Mike McCauley [EMAIL PROTECTED] wrote:
Yes, but you really should take into account the Acct-Delay-Time in
accounting requests, which is the amount of time the request has been
sitting in the NAS waiting for
So lets say I'm using MSSQL...
DateFormat %m/%d/%Y %X
AcctSQLStatementEXEC sp_acctinsert '%{Acct-S
ession-Id}','%{Acct-Status-Type}','%{User-Name}','%{TimeStamp}'
Should insert the TimeStamp as '9/11/2003 21:21:21' ???
The only time the DateFormat is
18 matches
Mail list logo
