"Andrew Staples" <[EMAIL PROTECTED]> wrote:
> We use a national dialup provider, thus they are the passthrough for all
> radius info between our server and a given NAS. The documentation for
> naspasswd states that I don't need entries in that file unless I'm using
> non-smtp queries, but I don't k
ECTED] On Behalf Of Evren
Yurtesen
Sent: Monday, February 02, 2004 5:32 PM
To: [EMAIL PROTECTED]
Subject: Re: clean_radacct integration
well you should configure clients.conf and naspasswd files also.
Evren
Andrew Staples wrote:
>
>
> -Original Message-
> From: [EMAIL PROT
well you should configure clients.conf and naspasswd files also.
Evren
Andrew Staples wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
As Alan said, configure and use checkrad to verify if users are still
active.
My reading of the docs/googl
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
>As Alan said, configure and use checkrad to verify if users are still
>active.
My reading of the docs/googling on "checkrad" indicates I just add this line
to radius.conf:
checkrad =/usr/local/sbin/chec
"Andrew Staples" <[EMAIL PROTECTED]> wrote:
> We are using SQL modules for accounting with freeradius. Often, we don't
> get the stop accounting packet from the NAS. This means the user
cannot log
in again until we manually clear the accounting entry in the radacct
table.
If your not getting st
"Andrew Staples" <[EMAIL PROTECTED]> wrote:
> We are using SQL modules for accounting with freeradius. Often, we don't
> get the stop accounting packet from the NAS. This means the user cannot log
> in again until we manually clear the accounting entry in the radacct table.
Why?
If you're u
We are using SQL modules for accounting with
freeradius. Often, we don't get the stop accounting packet from the
NAS. This means the user cannot log in again until we manually clear the
accounting entry in the radacct table. Timeout is set for 15 minutes, but
it doesn't look like that set
7 matches
Mail list logo
