Hello Rolando -
On Tue, 12 Feb 2002 01:03, Rolando Riley wrote:
When I say 'fairly accurate' - if your NAS fails to deliver a STOP record
to radiator, the user will not be removed from the online users database.
The above seems to be very common to happen. That is
1) hanged users which
Hello Neil -
This is really a question for your NAS vendor - sounds like a bug to me.
regards
Hugh
On Tue, 12 Feb 2002 08:54, neil d. quiogue wrote:
Hello,
Does anyone have an idea on what can cause the Acct-Session-Time to be 0?
I saw two types of Terminate-Causes: User-Request and
Hi Dave -
You are correct again - this *is* a Handler parameter (I mistook it for
AddToReply). However it is only supported in Radiator 2.19 and later.
My apologies.
regards
Hugh
On Tue, 12 Feb 2002 00:37, Dave Kitabjian wrote:
Oh, thanks. Note, however that:
6.16.19 AddToRequest
Hello Rolando -
On Tue, 12 Feb 2002 08:23, Rolando Riley wrote:
Hi Hugh:
I want to say that AuthBy DYNADDRESS work excellent so far for what I need
=)). Although I've got some doubts from my tests.
1) I noticed that when I ran radpwtst like the following:
Hi Shane -
Just add this code to the bottom of your radius.cfg
file (or whatever you call yours)
SessionDatabase SQL
DBSourcedbi:ODBC:RadiusLog
DBUsernameradiususer
DBAuthradiususerpassword/SessionDatabase
Where :
- RadiusLog is your ODBC datasource setup for
Radiator (you probably
We get tons of these with Ascend-Disconnect-Cause = 46 when 64k ISDN
customers misconfigure thier end and keep trying to bring up the second
channel. Every few seconds, their second channel will connect,
authenticate, and disconnect, resulting in lots of Acct-Session-Time = 0
sessions.
On Tue,
Hello Sam -
Can you send me a copy of your configuration file (no secrets) together with
a trace 4 debug showing what happens in both cases? And what version of
Radiator are you running and on what hardware/software platform?
thanks
Hugh
On Tue, 12 Feb 2002 10:25, Sam Nilsson wrote:
We
