[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Help-gnu-radius] still something odd with authentication
From: |
Riikka Rikkola |
Subject: |
[Help-gnu-radius] still something odd with authentication |
Date: |
Wed, 17 Sep 2003 11:37:27 +0300 (EEST) |
I changed users-file so that I wouldn't need to deal with sql, now it
looks like this:
koira Auth-Type = Local,
Password = "koira123"
Service-Type = Framed-User,
Framed-Protocol = PPP
riikka Auth-Type = Local,
Password = "riikka123"
Service-Type = Login-User,
Cisco-AVPair = "shell:autocmd = access-enable 192.168.8.2
timeout 10"
But I'm really confused why there was error related with sql
authentication in radius.log:
Auth.notice:(AUTHREQ local 60 riikka): Login OK [riikka], CLID unknown
Auth.error:(AUTHREQ local 61 koira): SQL authentication not available
Auth.notice:(AUTHREQ local 61 koira). Invalid user [koira], CLID unknown
So, why does there come complaints about sql if authentication type is
local? And what does this "CLID unknown" mean?
And I was really surprised that there wasn't any error related to
Cisco-AVPair-line. Is is correct?
On Tue, 16 Sep 2003, Sergey Poznyakoff wrote:
> Riikka Rikkola <address@hidden> wrote:
>
> > Auth.error:(AUTHREQ local 39 -v): SQL authentication not available
> > Auth.notice:(AUTHREQ local 39 -v): Invalid user [-v], CLID unknown
>
> Radauth is a script that depends on a `#!' feature of your shell.
> Evidently your shell is not able to pass any options to it, so please
> use the simple syntax `radauth username password'.
>
> > How can I get SQL authentication available?
>
> 1) Configure the package with --with-mysql, --with-postgres or --with-odbc
> option, depending on the database you are running. Please read the
> file README in the main distribution directory before doing that.
> The file contains the description of all configure options as well
> as the description of (hopefully) all most frequently encountered
> problems when using them. If you encounter any problems not described
> there -- write to the list. When running configure, pay attention
> to the messages regarding the SQL interface you have selected. If they
> say `no', then it means you have missed something/
>
> 2) Recompile the package. After that run `radiusd/radiusd --version' and
> examine the `Compilation flags' line. If it contains the word
> describing your SQL interace (USE_SQL_MYSQL for --with-mysql,
> USE_SQL_POSTGRES for --with-postgres, or USE_SQL_ODBC for --with-odbc),
> then everything is OK. If not -- return to the step (1).
>
> 3) Once you have compiled radiusd with the support for your preferred
> SQL, read the section `Creating SQL database' in the README and create
> your database following the instructions in this section.
>
> 4) When you have your database configured, populate it with the records
> necessary for the authentication.
>
> 5) Modify your raddb/sqlserver to fit your SQL database. For more
> information about that please refer to the accompanying documentation.
> The online copy of it is available in various formats at
> http://www.gnu.org/software/radius/manual.
>
> Regards,
> Sergey
>
>
>
>
>
> _______________________________________________
> Help-gnu-radius mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/help-gnu-radius
>
--
Riikka Rikkola address@hidden
Kauppakatu 7 D 36 gsm: 040-5207979
40100 Jyväskylä