[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-gnu-radius] CLID Unknown And Acct Errors Using MySQL
From: |
Sergey Poznyakoff |
Subject: |
Re: [Help-gnu-radius] CLID Unknown And Acct Errors Using MySQL |
Date: |
Fri, 04 Jan 2002 12:49:11 +0200 |
> What does CLID mean and why is it stopping my authentication?
CLID stands for Calling Station ID. It has nothing to do with the
authentication, and is included in messages for informational
purposes only.
> I saw earlier in the postings that the passwords have to be =
> encrypted...is this still true in 0.96 and will gnu-radius support plain
> text in the near future since that's how it is stored in my databases?
Yes, version 0.96 supports plaintext passwords in SQL databases. To
use plaintext passwords, the apporpriate `raddb/users' entry should
look like:
DEFAULT Auth-Type = Crypt-Local,
Password-Location = SQL
...
(ellipsis stands for any additional check and reply pairs you might
need).
More information about these matters can be found in accompanying
documentation (an online version of the documentation is available
at http://www.gnu.org/software/radius/manual).
> I'm guessing that Acct.warning: stat_update is happening because there
> is no record in there for it to update since the DB table is empty.
Not quite so. The reason for this warning is that the reported NAS
is not described in raddb/naslist. If you have a big number of NASes
you can use DEFAULT entry in raddb/naslist to prevent this warning
from appearing, e.g.:
# NAS Name Short Name Type Flags
#----------- ---------- ---- -----
DEFAULT other
> In the Acct.error what attributes are not found?
One (or more) of attributes listed in your acct_start_query. To
determine what attributes are missing, look into your detail file
(usually, /var/log/radacct/<nasname>/detail) and compare its contents
with the attributes, used in acct_start_query.
Actually, the diagnostics should be more verbose, I will fix it
soon.
> Also I have noticed that the program takes about 30 seconds to startup
> but it does not seem to be doing anything according to top.
To fix it, start radius with --do-not-resolve (or -n) option, to
prevent it from trying to resolve all the IPs it encounters in
naslist.
Regards,
Sergey