(RADIATOR) Problem with Authentication and accounting

Akinpelu akinpelu at microaccess.com
Mon May 27 05:33:12 CDT 2002


Hello,

I had configured the radiator 3.0 demo on my server and I use Cisco AS5300
as the NAS. But the authentication is still being done by the NAS and not
the radius server as expected.

Below is a copy of my radius.cfg:

<Client IP add. of the NAS>
        Secret 
</Client>
#<Client DEFAULT>
# Secret mysecret
# DupInterval 0
#</Client>
<Realm microaccess.com>
 <AuthBy FILE>
  Filename %D/users
 </AuthBy>
 # Log accounting to a detail file
 AcctLogFileName %L/detail
 MaximumSessions 1
</Realm>
AuthPort 1812
AcctPort 1813

Below is the configuration i have on the NAS:

aaa authentication login users radius
aaa authentication ppp users if-needed radius
aaa authorization network radius
aaa accounting network start-stop radius
radius-server host (IP add. of the radius server) auth-port 1812 acct-port
1813
radius-server key ...

Is there anything I have missed out? I will be glad is anybody can give me a
hint on what to do.

Thanks.

Akin.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20020527/14bcc22b/attachment.html>


More information about the radiator mailing list