Hi everone,
I am new to the field of Radiator. We are in a process
of testing it for our needs. I am running into some
problems and any help to it would be greatly
appreciated.
I am sending my radius.cfg file which is stored under
/usr/local/etc
directory. I am also sending a copy of my users file,
which contains the default user "mikem" as well as a
newly created user by the name "moin". I have
stored this file at both /etc/radiator and
/usr/local/etc directories. I did
not change anything else from the initial config.
Please note that i have removed the IP address of our
client from the file and replaced it with "a.b.c.d"
The "radpwtst" command works
properly and its output is
sending Access-Request...
OK
sending Accounting-Request Start...
OK
sending Accounting-Request Stop...
OK
As far as the hardware config is concerned, Its a
Linux box with Redhat on it,
933 Mhz P III processor, 256 MB RAM, 35 GB hard disk,
etc.
Please take time to view the config and suggest
anything i need to change. Is there something that i
am overlooking.
U can also reach me at 303 735 4809. Thanks.
Imran.
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
# radius.cfg
#
# Example Radiator configuration file.
# This very simple file will allow you to get started with
# a simple system. You can then add and change features.
# We suggest you start simple, prove to yourself that it
# works and then develop a more complicated configuration.
#
# This example will authenticate from a standard users file in
# the current directory and log accounting to a file in the current
# directory.
# It will accept requests from any client and try to handle request
# for any realm.
# And it will print out what its doing in great detail.
#
# You should consider this file to be a starting point only
# $Id: linux-radius.cfg,v 1.1 2001/05/17 05:33:34 mikem Exp mikem $
#Foreground
#LogStdout
LogDir /var/log/radius
DbDir /etc/radiator
# Use a low trace level in production systems. Increase
# it to 4 or 5 for debugging, or use the -trace flag to radiusd
Trace 3
# You will probably want to add other Clients to suit your site,
# one for each NAS you want to work with
# THIS IS THE 5500 CLIENT- ATTEMPTING A NON-NAMESERVED ENTRY
<Client a.b.c.d>
Secret imran
</Client>
<Client DEFAULT>
Secret mysecret
DupInterval 0
</Client>
<Realm DEFAULT>
<AuthBy FILE>
Filename %D/users
</AuthBy>
# Log accounting to a detail file
AcctLogFileName %L/detail
</Realm>
<Realm backbone>
<AuthBy FILE>
Filename %D/users
</AuthBy>
# Log accounting to a detail file
AcctLogFileName %L/detail
</Realm>
# users
# This is an example of how to set up simple user for
# AuthBy FILE.
# The example user mikem has a password of fred, and will
# receive reply attributes suitable for most NASs.
# You can do many more interesting things. See the reference
# manual at /usr/share/doc/Radiator-2.18.1/ref.html
#
# You can test this user with the command
# radpwtst
mikem Password=fred
Service-Type = Framed-User,
Framed-Protocol = PPP,
Framed-IP-Netmask = 255.255.255.255,
Framed-Routing = None,
Framed-MTU = 1500,
Framed-Compression = Van-Jacobson-TCP-IP
moin Password=pete
Service-Type = Framed-User,
Framed-Protocol = PPP,
Framed-IP-Netmask = 255.255.255.255,
Framed-Routing = None,
Framed-MTU = 1500,
Framed-Compression = Van-Jacobson-TCP-IP
