Hello Chris,
On Fri, 18 Jul 2003 12:05 pm, Chris wrote:
Hello list,
I'm using radmin + radiator, Right now I want to do these to my system,
please point me out to some examples or possible solutions:
1. How do I make first time users to base their starting usage from the
moment they first
Hi Chris,
My advice for different time zone u should be using a stored procedure to
process the accounting event. The person might be said surfing 11pm and end
@2am. u will be charging 11-12am and the rest free.
We have implementing the rating using the stored procedure and it allows
You could use an AcctSQLStatement that sets thir expiry date if it is
currently NULL. The the first successful session start will set their
expiry
date to, say the current date + 30 days (or whatever your policy is).
thanks mike should I be safe then if I add this to my AcctSQLStatement to
Hello Chris,
On Fri, 18 Jul 2003 09:56 pm, Chris wrote:
You could use an AcctSQLStatement that sets thir expiry date if it is
currently NULL. The the first successful session start will set their
expiry
date to, say the current date + 30 days (or whatever your policy is).
thanks mike
AcctSQLStatement update RADUSERS set VALIDFROM=now where VALIDFROM IS NULL
and
Oh, ok thanks I get it, now how can my Radmin database set VALIDFROM
initially to NULL, I tried to test it using radmin editUser.pl web script
and it gave out this error: Not updated because: Invalid date/time format
Title: Queries on proxy radius and config file auto refresh on Radiator Radius
Hi
I've just deployed Radiator Radius in my workplace but am facing some problems with having to make changes so often and creating many downtimes on my servers. Would appreciate if you can help me with the
Just kill -HUP the radiusd process when you've changed the configs
Clients won't notice the difference - the re-read of the configs is very
fast
-Original Message-
From: Brian CHNG Sing Yong [mailto:[EMAIL PROTECTED]
Sent: 18 July 2003 16:23
To: '[EMAIL PROTECTED]'
Cc: CHEW Yong Sin
Greetings,
I upgraded from an older version of Radiator to the latest. After making
a couple of simple mods to the config file, it seems Handlers aren't
being handled correctly.
But this appears in the log:
Fri Jul 18 13:23:22 2003: ERR: Bad attribute=value pair: Client-Id =
IPsentry
Fri Jul 18
Greetings...
I have been able to strip out the username and replace it with a new username
for our accounting information with every type of nas other than
portmaster's. I was wondering if anyone else had come up with a solution. I
have read in the archives of someone with a similar issue, but
You could use a PreHandlerHook in your Client clause like this-
Client XXX.XXX.XXX.XXX
Secret somesecret
PreHandlerHook sub
{${$_[0]}-change_attr('NAS-IP-Address','YYY.YYY.YYY.YYY');}
/Client
This may cause unintended consequences with your downstream RADIUS servers
since all
Radiator/Radmin is auth/acct for dialup users (MAX6000/PM3's), and also DSL
users(Cisco7200).
Dialup users acct data is successfully updated in the RADUSAGE table, but DSL clients
are not(RADONLINE is working for both).
I see the insert in trace4:
Sat Jul 19 08:05:51 2003: DEBUG: do query is:
Hello Brian -
For your first question, you can use the AuthBy SQLRADIUS clause for your radius proxy targets, and you can use a Client DEFAULT to match any number of client devices.
Client DEFAULT>
.
/Client>
See section 6.45 in the Radiator 3.6 reference manual (doc/ref.html).
For your
Hello Tim -
This looks like an error in the configuration file, probably in an AddToReply or similar.
Without seeing the configuration file it is hard to say for sure.
regards
Hugh
On Saturday, Jul 19, 2003, at 03:28 Australia/Melbourne, Timothy G. Wells wrote:
Greetings,
I upgraded from
Hello Michael -
A more usual and portable method of doing this is to use the Class
attribute and log it in your accounting.
AddToReply Class = [EMAIL PROTECTED]
regards
Hugh
On Saturday, Jul 19, 2003, at 04:18 Australia/Melbourne, Michael
Shoemaker wrote:
Greetings...
I have been able to
14 matches
Mail list logo
