(RADIATOR) testing radiator with mysqlradiator at open.com.au
Hugh Irvine
hugh at open.com.au
Thu Apr 28 17:46:24 CDT 2005
Hello Ted -
The first message is just a warning and is innocuous - you can define a
default host in the AuthBy SQLRADIUS clause if you wish.
See sections 6.4.7 and 6.4.8 in the Radiator 3.12 reference manual
("doc/ref.html").
The second problem is due to the configuration file definition of "."
for DbDir (and LogDir). In your case you would typically use
"/etc/radiator" for your configuration file, dictionary file and so on,
hence you should do something like this:
# Radiator configuration file
.....
# set DbDir to /etc/radiator
# for configuration file, dictionary, etc.
DbDir /etc/radiator
# set LogDir for logging
LogDir /var/log/radius
.....
regards
Hugh
On 29 Apr 2005, at 06:37, Theodore Knab wrote:
> Hi am trouble testing/ configuring radius for use with the mysql
> stuff.
>
> I get this error when I try to run the radiator. What does this mean
> and how can I fix it ?
>
> I included the error message and the config file.
>
> This is a debian sarge system:
> I used alien -i to install the rpm.
>
> easy:/etc/radiator# /etc/init.d/radiator start
> Starting Radiator: Thu Apr 28 16:25:46 2005: WARNING: No Hosts
> defined for Radius::AuthSQLRADIUS at '/etc/radiator/radius.cfg' line
> 76
> Thu Apr 28 16:25:46 2005: DEBUG: Finished reading configuration file
> '/etc/radiator/radius.cfg'
> This Radiator license will expire on 2005-10-01
> This Radiator license will stop operating after 1000 requests
> To purchase an unlimited full source version of Radiator, see
> http://www.open.com.au/ordering.html
> To extend your license period, contact admin at open.com.au
>
> Thu Apr 28 16:25:46 2005: DEBUG: Reading dictionary file
> './dictionary'
> Thu Apr 28 16:25:46 2005: ERR: Could not open dictionary file
> './dictionary': No such file or directory
> Couldn't create dictionary from './dictionary'. Check log for more
> information: Inappropriate ioctl for device at (eval 8) line 446.
> ...caught at /usr/bin/radiusd line 5.
>
> I have a host listed:
>
> mysql> select * from RADSQLRADIUS;
>
> +------------+---------------+----------------+-----------+----------
> +----------+---------+--------------+-----------------------
> +----------------------------+--------------------------
> +----------------------+---------------+
> | TARGETNAME | HOST1 | HOST2 | SECRET | AUTHPORT
> | ACCTPORT | RETRIES | RETRYTIMEOUT | USEOLDASCENDPASSWORDS |
> SERVERHASBROKENPORTNUMBERS | SERVERHASBROKENADDRESSES |
> IGNOREREPLYSIGNATURE | FAILUREPOLICY |
>
> +------------+---------------+----------------+-----------+----------
> +----------+---------+--------------+-----------------------
> +----------------------------+--------------------------
> +----------------------+---------------+
> | r1 | radius_tester | 209.243.33.239 | tester123 | NULL
> | NULL | NULL | NULL | NULL
> | NULL | NULL
> | NULL | NULL |
>
> +------------+---------------+----------------+-----------+----------
> +----------+---------+--------------+-----------------------
> +----------------------------+--------------------------
> +----------------------+---------------+
> 1 row in set (0.00 sec)
>
>
> # sqlradius.cfg
> #
> # Example Radiator configuration file.
> # This very simple file will allow you to get started with
> # a simple AuthBy SQLRADIUS system.
> #
> # AuthBy SQL looks up a target radius server for every request in an
> # SQL database, then proxies to the target server. It uses the realm
> # as the default lookup into the database.
> #
> # It is useful for managing large numbers of downstream radius servers
> #
> # Requires a suitable table in an SQL databse. See goodies/*.sql for
> example
> # tables. Some sample data for a simple system:
> # insert into RADSQLRADIUS (TARGETNAME, HOST1, HOST2, SECRET)
> # values ('r1', 'oscar', '203.63.154.2', 'mysecret');
> # insert into RADSQLRADIUS (TARGETNAME, HOST1, SECRET)
> # values ('r2', '203.63.154.2', 'yy');
> #
> # You can have much more complicated things, including indirect lookups
> # where multiple realms all map to the same target server.
> #
> # See radius.cfg for more complete examples of features and
> # syntax, and refer to the reference manual for a complete description
> # of all the features and syntax.
> #
> # You should consider this file to be a starting point only
> # $Id: sqlradius.cfg,v 1.1 2001/10/26 05:37:06 mikem Exp $
>
> Foreground
> LogStdout
> LogDir .
> DbDir .
> # User a lower trace level in production systems:
> Trace 5
>
> # You will probably want to add other Clients to suit your site,
> # one for each NAS you want to work with
> <Client DEFAULT>
> Secret mysecret
> DupInterval 0
> </Client>
>
> <Realm DEFAULT>
> # This uses the users realm to look up the target
> # radius server in an SQL database
> <AuthBy SQLRADIUS>
> DBSource dbi:mysql:radiator:albert.washcoll.edu
> DBUsername radiator
> DBAuth gatsby555
>
> # The default HostSelect query will look up according
> # to realm in a table called RADSQLRADIUS, see
> # goodies/*.sql for examples
> # You can use HostSelect SQL query to work with
> # your own table def, eg:
> HostSelect select HOST1, SECRET from RADSQLRADIUS
> where TARGETNAME='%R'
> NumHosts 1
>
> # Alternatively, you could do the lookup based on
> # eg Called-Station-Id:
> #HostSelect select HOST%0, SECRET, AUTHPORT, ACCTPORT,
> RETRIES, RETRYTIMEOUT, USEOLDASCENDPASSWORDS,
> SERVERHASBROKENPORTNUMBERS, SERVERHASBROKENADDRESSES,
> IGNOREREPLYSIGNATURE, FAILUREPOLICY from RADSQLRADIUS where
> TARGETNAME='%{Called-Station-Id}'
>
> # If you have lots of Realms or Called-Statrion-Ids
> # that map to a single
> # target radius server, you can use the example
> # RADSQLRADIUSINDIRECT table to define the mappings
> # and HostSelect would be a join:
> #HostSelect select R.HOST%0, R.SECRET, R.AUTHPORT,
> R.ACCTPORT, R.RETRIES, R.RETRYTIMEOUT, R.USEOLDASCENDPASSWORDS,
> R.SERVERHASBROKENPORTNUMBERS, R.SERVERHASBROKENADDRESSES,
> R.IGNOREREPLYSIGNATURE, R.FAILUREPOLICY from RADSQLRADIUS R,
> RADSQLRADIUSINDIRECT I where I.SOURCENAME='%R' and
> I.TARGETNAME=R.TARGETNAME
>
>
> # You can define <Host> clauses here like in AuthBy
> RADIUS.
> # They will be used to proxy requests that do not
> # have an entry in the database (ie HostSelect returns
> # no rows. Use this mechanism to handle default realms.
> </AuthBy>
> </Realm>
>
>
>
>
>
> --
> --------------------------------------------------------|
> *Theodore Knab |
> *Washington College |
> ---------------------------------------------------------
> When the ego takes charge of a situation, the rational |
> self is out of control. |
>
>
>
NB:
Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive
(www.open.com.au/archives/radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.
--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.
More information about the radiator
mailing list